[KS-370] Pass config from onchain registry to execute calls

[cedric-cordenier]

https://smartcontract-it.atlassian.net/jira/software/c/projects/KS/boards/182?assignee=712020%3A25361daa-6eb8-4a03-9963-0264ac70a192

• This passes config from the onchain capabilities registry to the capability itself, allowing some config settings (eg. deltaStage, schedule) to be specified as capability config, not as workflow config).
• Refactor the registrysyncer: this now returns a LocalRegistry object on each sync iteration with methods for fetching the local node and capability-specific config.
• Add methods from the LocalRegistry to the CapabilitiesRegistry as well, so they can be passed to LOOPified capabilities.

Requires Dependencies

smartcontractkit/chainlink-common#640

Resolves Dependencies

[github-actions]

I see you updated files related to core. Please run pnpm changeset 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.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
1 Fixed issue
0 Accepted issues

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

See analysis details on SonarQube

PR updated