Feature Request (DX) - introduce structure to send multiples contexts for several policies at the same time

Hi ACE Team,

My name is Vitali Grabovski, and I have been working on on-chain compliance infrastructure for five years at my company.
I came across this project through a thread on the Ethereum Magicians forum where someone asked about the similarities and differences between ACE and ERC-8006. That discussion caught my attention and motivated me to create this issue.

Motivation
What I found missing in ace is a lack of standardized way to provide context for multiple policies. It seems that when 3 or more policies share the same context, the lack of a defined structure for context can quickly become a mess.

Suggested Approach
Based on this, I think the following points are missing:

• context should be supplied for every policy that requests it

• empyt context should be supplied for every other policy

• each requested context should be validated against non-zero value

• each requested context should be validated against valid payload

• each policy should know how to retrieve its own context from the shared context returned by getContext(); alternatively, the specific policy context must be provided to the policy

Without such standardization, developers will likely need to implement ad hoc methods such as setContextA(), setContextB(), setContextC(), ..., setContextX() in contracts that inherit from PolicyProtected.

In addition, getContext() ends up taking responsibility for packing the context payloads for each policy, including zero payloads for those that don't require context. Developers are forced to override getContext() to implement their own packing logic.

Most importantly, every policy must then implement custom unpacking code that depends on the specific getContext() implementation written by the developer. DX significantly degrades this way.

Start by reading the PolicyProtected contract and the getContext() flow, then trace how policies currently receive, validate, and unpack context. Define the scope and acceptance criteria for a standardized multi-policy context structure, including empty contexts and policy-specific retrieval, before identifying the affected contracts and tests.