Update require statements in client-side code use impot/export syntax

[naglepuff]

We currently have some light mixing of ES6 style import/export syntax and common JS require. I'm specifically referring to the use of images for the study detail page:

nmdc-server/web/src/views/IndividualResults/StudyPage.vue

Lines 222 to 229 in da8bb30

	images: {
	// eslint-disable-next-line global-require
	gold: require('@/assets/GOLD.png'),
	// eslint-disable-next-line global-require
	ess: require('@/assets/ESS.png'),
	// eslint-disable-next-line global-require
	massive: require('@/assets/massive.png'),
	},

And the biosample detail page (see PR #1577).

I think it would be good to favor one style of imports over the other. The vast majority of our code base uses import/export, so we should update to statements like:

import gold from @/assets/gold.png

In order to appease typescript, we might also need to add a type declaration file so it knows how to treat these imports. Something like: https://stackoverflow.com/a/54137233