Setup GitHub Release for Production Deployments

[NEStock]

I'd like to suggest that we revert back to using GitHub Releases to start the production deploy and have a single default prod (or differently named) branch that sandbox (and production) deploys from.

Pros:

• Prevent the curret "double" PR workflow that we have to do now
• Clean up our commit history
• Makes the merging more straightforward

For reference, our current workflow is as follows:

1. new branch for an issue <issue-branch>
2. merge <issue-branch> into apl-setup
   a. apl-setup branch is deployed to the Sandbox App https://apl-setup--ember-dandi-archive.netlify.app/
3. merge apl-setup to prod
   a. prod branch is deployed to the Production App https://dandi.emberarchive.org

Welcome additional thoughts & pros/cons!

[NEStock]

Additional Note: if/when we do this, we will want to un-skip the test in homePage.test.js checking for the version link!

[yarikoptic]

probably that should also address the issue of incorrect describe on the mainpage:

or do you just need tags?

[NEStock]

probably that should also address the issue of incorrect describe on the mainpage:

or do you just need tags?

My understanding is that if we used tags then the version would show up in more user-friendly way (i.e. version v0.13.1) , like on https://dandiarchive.org

So I think yes using releases would also achieve this