Design the setup

Most likely this repo would
- "bind" versions of dandi-schema, dandi-archive and dandi-cli destined/tested/specified to work together
- git submodules sounds like a good idea but likely NOT the solution to use since we might want to establish ranges of versions (in particular dandi-cli) which could be used with other (ranges of versions) of other components. That would allow to test "min" and "max"
- @candleindark mentioned that linkml uses some "workspaces" concept in pyproject.toml which does something similar to bring together components https://github.com/linkml/linkml/blob/main/pyproject.toml

- we might want to retrospectively create such versioned bundles
-

TODO: fill out more...

Refs:
- https://github.com/dandi/dandi-infrastructure/issues/247

Read the referenced LinkML pyproject.toml and dandi-infrastructure issue #247 first, then compare how dandi-schema, dandi-archive, and dandi-cli are currently versioned. A completed result should specify how compatible version bundles are represented, including min/max testing and any retrospective bundles.

Written by the indexing model from the issue text.