Add option to use (metadata of) assets already in the archive for the dandiset

I think this is the use case @satra having in mind which resulted in https://github.com/dandi/dandi-cli/issues/1163 , where we need to organize just some subset of locally present assets and have no other assets available locally. Then @satra envisions that `dandi` (during `organize` and/or `upload`) somehow (an exact algorithmic procedure was not yet formulated) would use assets metadata from archive to ensure "correct" disambiguation.

Having (only briefly) thought about it, I am not yet sure about possibility of a clean algorithmic procedure which would satisfy us. I think that we might "alternatively" make it more explicit by

- addressing https://github.com/dandi/dandi-cli/issues/69
- which in turn likely address https://github.com/dandi/dandi-cli/issues/1000

and would allow user to explicitly state for a given dandiset which metadata entities to use, and thus make any *partial dandiset organize* be consistent with the case if it was done on an entire dandiset across all files. WDYT @satra ?