Decouple static workflow graph validation from execution state

[krehermann]

The change pre-sages refactoring the workflow validation into chainlink-common for use by CLO.

The point of the change is to decouple the notion of valid yaml (that forms a graph) from the notion of an executable workflow whose steps have mutable step that are updated by the engine when it's executed.

To achieve that, we introduce a StaticWorkflow that is only the intermediate representation from parsing YAML into a valid graph.

Given this graph, we convert it to the pre-existing notion of a workflow.

The next change will be to move the StaticWorkflow into chainlink-common, which is the reason that it's public to start.

[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
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube