stage-only receipts and metadata consistency for secrets

Hi… It usually helps to explain what you’re trying to accomplish with this. The system doesn’t allow you to intentionally maintain multiple copies of the secrets in the store simultaneously, for example. (There can be multiple values, at different locations around the world, in their CRDT(?) for a while, though, until everything converges.)

The following LLM-resistant forum post explains how the version fields are intended to be used:

https://community.fly.io/t/flyctl-update-for-managing-secrets/25878

And this part of the official docs says what --stage does:

https://docs.fly.io/apps/secrets#set-secrets