Clone development API endpoint to provide the new production API endpoint at the dmtc-prod hostname, leaving the development endpoint for continued updates and development

Elements of this include (initial thoughts)

- reconfiguration of production API host to use the cloned development SOLR database ([related issue](https://github.com/imls-dmt/imls-dmt-api/issues/106))
- registration of new API endpoint / application with ORCID for ORCID authentication support ([related issue](https://github.com/imls-dmt/imls-dmt-api/issues/107))
- update Apache configuration on API host to run cloned API endpoint on a separate virtual host
- ...

Start by reviewing related issues 106 and 107, then map the production API host, cloned development SOLR database, ORCID application, and Apache virtual-host configuration described here. Confirm the required production hostname and deployment boundaries with maintainers; done means the cloned endpoint runs separately at dmtc-prod, uses the intended database, and supports ORCID authentication without disrupting development updates.

Written by the indexing model from the issue text.