(DRAFT/placeholder) get_metadata destiny

[yarikoptic]

With #1076 in its current form ATM we have following uses for get_metadata

$> git grep '[^.]get_metadata(' | grep -v 'def '
dandi/cli/cmd_ls.py:                    rec = get_metadata(path)
dandi/metadata.py:    metadata = get_metadata(nwb_path)  # within nwb2asset
dandi/organize.py:                meta = get_metadata(path)

which I would like to discuss on either / how should be addressed. So pretty much we have three uses left and an aspect is either they should operate on files bound to some dandiset or should be usable outside of any dandiset.
.... TODO: more to come

[yarikoptic]

now (0.51.0) we have

❯ git grep '[^.]get_metadata(' | grep -v 'def '
dandi/cli/cmd_ls.py:                        rec = get_metadata(path, Digest.dandi_zarr(digest))
dandi/cli/cmd_ls.py:                        rec = get_metadata(path, Digest.dandi_etag(digest))
dandi/consts.py:#: `get_metadata()`
dandi/files/bids.py:    # get_metadata(): inherit use of default metadata from LocalFileAsset
dandi/metadata.py:    metadata = get_metadata(nwb_path)
dandi/metadata.py:       returned by `get_metadata()`
dandi/organize.py:                meta = get_metadata(path)
dandi/tests/test_metadata.py:    metadata = get_metadata(simple1_nwb)
dandi/tests/test_metadata.py:    metadata = get_metadata(file_path)
docs/design/python-api-1.md:        * `get_metadata() -> DandisetMeta`
docs/design/python-api-1.md:        * `get_metadata() -> BareAssetMeta`
docs/design/python-api-1.md:        * `get_metadata() -> DandisetMeta`
docs/design/python-api-1.md:        * `get_metadata() -> RemoteAssetMeta`

so operating on other data types (zarr) and seems used, so let's let this RiP for now