Mega-issue: Vendorization of the dandi-schema and other components

[yarikoptic]

• see how to make our model to make instance parametrizable based on a specific instance of a Config passed into it: decided to go with "import time" configuration

• devendorize and allow import-time specification via env variables

  • tobemerged Initial Multi-DANDI instance support: import time - generic regexes by default + instance config #294
    • potentially be more "uniform" and gain DJANGO_ prefix: Provide environment variable aliases for setting instance config #322
  • Add vendorization of the Publisher for to_datacite #303
  • that would allow dandi-cli to already upload to any DANDI archive but only with generic, not vendor specific (unless env vars are set), validation

• make dandi-archive expose vendorization config as part of its /server-info (e.g. https://dandiarchive.org/server-info) as schema_vendorization record with vendorization parameters it loads from e.g. env vars (TODO: issue/PR against dandi-archive) @candleindark

  • tobe-rereviewed/merged Local runtime schema serialization endpoints dandi-archive#2386
    • Have the api/info/ endpoint provide instance config info dandi-archive#2430 (based on above #2386)
    • with #2430 in mind address De/re-vendorize dandi-archive dandi-archive#2382

• changes needed against TF configurations

  • Allow vendor specific info to be provided dandi-infrastructure#224
  • Allow vendor specific info to be provided lincbrain/linc-archive-infrastructure#24

• not needed: make dandi-cli validation paths (CLI validate and upload) be able to use specific instance validation record (validation - add support for vendorization record from the instance server dandi-cli#1625)