🔐 Document and decentralize Treasury operations

[JFWooten4]

e771f4e adds a key management page, which has a lot of work to do. First, we need to spell out all the IAM keys and identity access more broadly, working on in IAM Permissions, Roles, & Identities. This subsection can start the mapping of team --> AWS.

Second, and more significantly, this PR explains the distribution of keys for 1846058*blocktransfer.com. There could be a future extension of Exhibit 1.24; however, I want to keep that with just us and the regulators for now. Once AWS is set up, we can doc the existing (suboptimal) hot operations, which will then lead into a chat on Secrets Manager.

[JFWooten4]

This blocks the comment migration of Response PDFs in all forums, which I don't think is otherwise mentioned after the naïve implementation in physical notes for https://github.com/WhyDRS/documents

[JFWooten4]

It's questionable whether our operating keys themselves should really be under the S-P project, since they aren't actual inventory infram. But they could expand into that role based on the IPUFNS scoping growth. The present air-gapped access keys should be made to expand per the team distribution places, depending on how we set up the SEP12-sharing encryption with other agents.