[CRE-5456] Cache trigger subscription payloads

[bolekk]

Optimization to avoid executing all WASM workflows on node boot just to get trigger sub payloads.

Assumptiona:

• Trigger subs don't change across executions (if they do, things can break badly even before this change).
• Trigger subs don't contain secrets (already guaranteed by [CRE-6792] Disallow secrets calls during trigger subscriptions #23829).

Additionally treat empty subscriptions as a non-retriable user error.

Change under a TOML config flag. I used TOML instead of cresettings for two reasons:

• Flipping the flag requires a restart.
• Rollout will be safer per-node rather than per-org.

Deployment Validation:

1. None at image rollout - feature is off by default.
2. After enabling the flag:

• verify the number of active workflows hasn't changed and the number of failed registrations didn't go up.
• check for improvements in startup time.

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

   

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
3 New issues
16 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube