Update GitHub repo and supporting infrastructure for HTAN2 data model

[aclayton555]

Emerges from #448

Question: Do we want to set up a new repo for the HTAN 2.0 data model? If so, what, if any, remaining updates should be made within the HTAN 1.0 data model repo?

Yes, new HTAN 2.0 repo and supporting infrastructure (e.g. phase 2.0 DCA) to be set up and supported in parallel with remaining maintenance of HTAN 1.0 model and infrastructure (i.e. keep the door open and working for HTAN 1.0 submissions). Stuff will be pulled over to a new repo for HTAN 2.0. Timeline TBD for final sunset/shutdown/archive of phase 1.0 infrastructure, but for now, no changes are needed to this current data model repo.

Decide to do before cloning (?) over a new repo for HTAN 2.0

• Action to auto-generate blank templates upon data model release #461

Supporting activities

• Adopt semantic versioning #462

[aclayton555]

24-11/12 Close-out: Discussed with Aditi, Adam, Darya, and Kristen. Agreed not to set up a new repo, but we should create a new, blank branch for development purposes to keep HTAN1 and HTAN2 Data Models partitioned. Ashley also in favor of this approach to retain existing link to data model repo (which is embedded in various resources) and to maintain existing backlog without having to move issues. See #470

To-do: Update existing repo (e.g. README, etc) to ensure organization and operations maintain partitioning between HTAN1 and HTAN2 Data Models.

[aclayton555]

Related tickets to update repo:

• Adopt semantic versioning #462
• Create HTAN2 Data Model feature branch #470
• Review and update README #475