Clarity docs: tag epoch-dependent DocNotices with their activation epoch #7746

Is your feature request related to a problem? Please describe.
The docs site gets its Clarity reference from stacks-inspect docgen; a weekly bot PR regenerates it from main. The function docs in clarity/src/vm/docs/mod.rs already describe Epoch 4.1 behavior (also in 4.0.5), so https://docs.stacks.co/reference/clarity/functions shows rules that are not active on mainnet.

Seven passages are affected: two DocNotices (fold, tuple) and five in descriptions (principal-destruct?, from-consensus-buff?, define-public, define-read-only, define-trait). The define-read-only sentence does not name the epoch, so it reads as a current rule: https://docs.stacks.co/reference/clarity/functions#define-read-only

Describe the solution you'd like
My question: can DocNotice get an optional epoch: Option<StacksEpochId> field? The five description passages would move into notices, and all seven would get epoch: Some(StacksEpochId::Epoch41). The docs generator then reads current_epoch from /v2/pox and hides notices for epochs that are not active, so the notes appear on their own when 4.1 activates.

If yes, do you want me to open the PR, or do you prefer to do it?

Describe alternatives you've considered
If you prefer no format change: start the define-read-only sentence with "Beginning in Epoch 4.1,". Then every passage names its epoch, and I keep them as they are.

Additional context

• Source: https://github.com/stacks-network/stacks-core/blob/4.0.5/clarity/src/vm/docs/mod.rs (DocNotice at L41-L46, define-read-only at L2357)
• Bot PR: chore: sync Clarity reference from stacks-core docs#1894