Issue Summary:
Forge function doesn't receive the workflow validator configuration field in the payload during Jira issue transitions, blocking development and causing significant performance overhead. According to the Jira events, the configuration should be present under configuration, but it's missing from the payload received by workflow validator Forge functions.

Expected Results:
The payload received by the Forge function during a workflow transition should include the validator configuration, matching what is available in the UI context.

Actual Results:
The payload received by the Forge function doesn't include the validator configuration. Only basic issue and transition information is present. As a result, developers must implement a multi-step workaround to retrieve the configuration, which negatively impacts performance and increases API usage.

Workaround:
Currently, there isn't a known workaround from Atlassian for this behavior that avoids significant performance penalties. A workaround has been implemented by the partner which comprises:

• Decode the context token

• Extract the extension ID

• Use the Jira REST API to fetch workflows and match against project/extension ID

• Extract the validator config from there

This process is slow and resource-intensive.