Epic: Addresses & Keys Changes

[iAmMichaelConnor]

Following several rounds of discussions and decisions, here's a list of tasks relating to changes to addresses & keys.

### New address scheme
- [ ] Write an eng design doc for the new address scheme. Liaise w/ other teams (esp AVM).
- [ ] Implement the new address scheme across the stack
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8966

### Keys
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/9162
- [x] Remove code relating to key rotation
- [x] Remove the key registry
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8969
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8970
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8999
- [ ] P1: Internal Incoming Viewing Keys

### p1: Plume
- [ ] Liaise w/ Crypto Research to ensure security of approach for Plume w/ Grumpkin & Posiedon2 [Mike to do]
- [ ] Run the latest flamegraph of the reset private kernel circuit, to determine the constraint counts for one key validation request. Compare it against 3300 for plume.
- [ ] Implement an example flow of using plume nullifiers.
- [ ] Fun: Explore how to add Grumpkin ops as an 'app' on Ledger hardware wallets.
- [ ] Example Escrow contract

[nventuro]

The key registry was removed in #8613, and key rotation was then fully removed in #8645.

[rahul-kothari]

Marking plume and internal incoming keys as p1 (i.e. post testnet)

[sklppy88]

#9326, #8966, #8969 are resolved by the stack at #9272, with some enhancements in later PRs in the stack.

[sklppy88]

After replacing npk_m_h with address in https://github.com/AztecProtocol/aztec-packages/pull/9461, we can send notes to users without their public keys !

This means registerRecipient is unnecessary now, and was nuked in https://github.com/AztecProtocol/aztec-packages/pull/9548.

I think this concludes P0 tasks here with the full initial implementation of the new address and keys changes ?