Mandate that signed payloads are endpoint-specific and timestamped in Programmability sample

[achamayou]

See remaining item on #6223. Introduce DynamicJSEndpointRegistry::record_action_details_for_audit_v1 and DynamicJSEndpointRegistry::is_original_action_execution_v1 to allow an application making use of the programmability feature to easily implement auditability, and protect users allowed to update the application against replay attacks.

This allows an application to define two parameters in the protected header of COSE Sign1 envelopes, for the purposes of:

1. Making payloads specific to an endpoint, to avoid possible confusion attacks
2. Making payloads timestamped, to implement replay protection cheaply

I have hardcoded the window size for now, but moving it to the runtime_options may be a good idea, perhaps as cose_replay_protection_window_size, or something similar. It's difficult to imagine this being useful though.