Validate keystone workflows + Enforce full semver on capabilities

[HenryNguyen5]

This PR contains the following changes:

• Workflow definitions now enforce that a full capability semver must be specified. No version ranges are allowed.
• Validation for workflow YAMLs is now enabled.
• The CapabilityInfo struct now embeds the version as part of the ID itself, rather than having it as a separate field.

Prior arts:

• [Keystone] Merge version field with ID #13136
• Enable workflow validation against JSON spec #13125

Related PR: smartcontractkit/chainlink-common#536

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[DeividasK]

The owner needs to be within the workflow spec (not the "job spec for the workflow"), as the nodes will need to get the owner from the workflow after validating signatures, right?

[HenryNguyen5]

I'm not too sure, I kept the structure of the test cases the same as trunk. I think we should address this in a separate topic as I want to get validation for workflow specs (not job specs) merged in first.

[cedric-cordenier]

@DeividasK It's not part of the workflow spec (at least it wasn't last time I checked). We do pass it from the workflow spec to the RequestMetadata thus making it available to capabilities though