DRAFT: fix(canary): schema validation for canary steps

[msfidelis]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed my commits with DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

[sonarqubecloud]

Quality Gate passed

Issues
0 New 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 Cloud

[github-actions]

Published E2E Test Results

  4 files    4 suites   2h 57m 39s ⏱️
 82 tests  50 ✅  4 💤  28 ❌
324 runs  202 ✅ 16 💤 106 ❌

For more details on these failures, see this check.

Results for commit fe17ef4.

[github-actions]

Published Unit Test Results

2 009 tests   1 998 ✅  2m 9s ⏱️
  129 suites      0 💤
    1 files       11 ❌

For more details on these failures, see this check.

Results for commit fe17ef4.