enh: add dandi-asset as an additional parameter to external services

[satra]

to address passing additional info this adds a new parameter for external services.

[yarikoptic]

why not just provide as a separate kwarg to be used in definition of the url to jump to in the service? i.e.

Suggested change

	url: `${service.endpoint}${trimEnd((path.asset as AssetFile).url, '/')}&dandi-asset=${assetMetadataURI((path.asset as AssetFile).asset_id)}`,
	url: `${service.endpoint}${trimEnd((path.asset as AssetFile).url, '/')}`,
	asset_id: `${assetMetadataURI((path.asset as AssetFile).asset_id)}`,

?

[yarikoptic]

AH -- I just now saw that we didn't follow the original design idea here and had only prefix for the url:

  {
    name: 'Neurosift',
    regex: /\.nwb$/,
    maxsize: Infinity,
    endpoint: 'https://flatironinstitute.github.io/neurosift?p=/nwb&url=',
  },

my bad -- we ideally would need to RF it to provide all those "format" kwargs, so here it would become

  {
    name: 'Neurosift',
    regex: /\.nwb$/,
    maxsize: Infinity,
    endpoint: 'https://flatironinstitute.github.io/neurosift?p=/nwb&url={url}&dandi-asset={asset_id}',
  },

or some other way java script allows for such embeddings...

[yarikoptic]

according to chatgpt JS/vue has similar to python f-strings so we can easily do that.

const struct = { field1: "value" };
const v = `something ${struct.field1}`;

[waxlamp]

Closing this as superseded by #1706 and its followups.