feat: reintroduce the mock streams trigger on develop

[cawthorne]

Summary

• forward-port the Aptos-init mock streams trigger onto develop
• gate registration behind an explicit local capability config entry so it stays test-only
• keep the dummy metadata registry F=1 behavior needed by the legacy workflow smoke path
• add focused tests for the gate and the mock trigger lifecycle/event path

Testing

• GOWORK=off go test ./core/capabilities/streams -run 'TestMockTriggerService|TestStreamsTrigger' -count=1
• GOWORK=off go test ./core/services/chainlink -run TestShouldRegisterMockStreamsTrigger -count=1

[github-actions]

✅ No conflicts with other open PRs targeting develop

[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.

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
0 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