Epic: Configurable K8s Clusters

[just-mitch]

Design

### Tasks
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/7999
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8000
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8001
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8004
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8506
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8831
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8822
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8828
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8507
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8006
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8002
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8005
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8007
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8027
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8026

[stevenplatt]

I have added staging and production branches to the repo. The intention is to allow developers to graduate the codebase into different stages of public release using git.

In practice the merge flow would be:

• master --> staging --> production

This flow could make it easier to allocate categories of tests to different stages of release.

In practice test allocation would be:

• local: active development (fast feedback)
• master: per PR, nightly (normal feedback)
• staging: soak testing, early access (slow feedback)
• production: general availability (passive monitoring)

What do you think @spypsy @ludamad ?

[ludamad]

Seems reasonable :)