Add allowlist database

[Mirko-von-Leipzig]

Summary

Adds a new sequencer-only database for holding account allowlist data.

This is a separate database because:

1. It is temporary, and
2. it requires a separate write path and I don't want to interfere with the chain data.

Changelog

[[entry]]
scope       = "node"
impact      = "added"
description = "Added a new sequencer database for tracking account allowlist"

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[SantiagoPittella]

should we make the invitation digest the PK?

[Mirko-von-Leipzig]

We can't because its optional :D

An admin is also allowed to inject an account ID directly without needing an invitation code.

[igamigo]

Would it be worth adding a notes column to this then? Something to write basic notes about who got the code, etc. Alternatively the invitation digest could be random and enforced and then we could get rid of id.

[igamigo]

Also should invitation_digest be indexed?

[Mirko-von-Leipzig]

I explicitly didn't want to track who got the code assigned here. I figured that could be done externally by whoever is handing them out. Otherwise we could also store the original code instead of the digest.

[igamigo]

Yeah, makes sense. IMO since this is supposed to be just for the closed mainnet and not a long term thing we could make it more immediately functional (eg if there is going to be a UI for editing the DB I think it could make sense to have notes there already, but the benefit is not substantial anyway so either way works for me; similarly for the actual invite code)

[Mirko-von-Leipzig]

That's fair; I was looking at it more from a perspective of who operates what i.e. sequencer operator is likely not the allowlist admin