Set up permanent branch deploys for testnets

[blushi]

Is your feature request related to a problem? Please describe. Currently, the development workflow only includes feature branches (that trigger Netlify deploy previews as soon as there's a corresponding PR) that get merged into master once approved (master auto-deploys to Netlify production apps). Deploy previews become unaccessible not long after the PR is closed. We would like to have permanent deploys instead for testing features on our 2 testnets (hambach and redwood).

Describe the solution you'd like We could create 2 branches (hambach and redwood) which would have different netlify.toml config for the different testnet endpoints (and possibly different front-end code logic for different versions of Regen Ledger) and use Netlify branch deploy feature: https://docs.netlify.com/site-deploys/overview/#branches-and-deploys. The only issue with that is that we need to come up with a clear new branching strategy. For instance, how to handle the development of features that are not related to testnets (e.g. a new component that should be used on all environments). Should we just use the current branching strategy (i.e. one feature branch that gets merged in to master) and then just backport this to the hambach and redwood branches? See notes from the architecture call below for more comments about that.

Additional context (optional) Notes from architecture call: https://www.notion.so/regennetwork/Interfaces-Architecture-2022-02-16-31242e21fa0f42398c89fd0cd54c4ca2

cc/ @clevinson @wgwz @haveanicedavid @mhagel @victordelval

---

For Admin Use

• [x] Not duplicate issue
• [x] Appropriate labels and zenhub epics applied
• [x] Appropriate contributors tagged

[blushi]

Hey team! Please add your planning poker estimate with ZenHub @haveanicedavid @mhagel @victordelval @wgwz

[blushi]

Updated the estimate to account for https://github.com/regen-network/regen-registry/issues/845#issuecomment-1060469848