FW-143 Add skynet config that verifies the github workflow passes

[wesleybalvanz-wf]

Motivation

Currently release pipelines are failing because they require a skynet run in order to pass the testing phase of the pipeline. We would like to not have to manually check that the github workflow passed and override the pipeline so we need a way to automatically check that the workflow passed and tell the pipeline that all is good.

Changes

Add a skynet.yaml that checks the github workflow run and passes or fails the skynet run depending on the results.

Release Notes

Add skynet run to check that the github workflow run passes

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• [ ] Tests were updated and provide good coverage of the changeset and other affected code
• [ ] Manual testing was performed if needed
  • [ ] Steps from PR author:
  • [ ] Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• [ ] A Client Platform member has reviewed these changes
• [ ] There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• [ ] For release PRs - Version metadata in Rosie comment is correct

[aviary3-wk]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure

• Verify aviary.yaml coverage of security relevant code

  Questions or Comments? Reach out on Slack: #support-infosec.

[todbachman-wf]

QA +1

[todbachman-wf]

@Workiva/release-management-pp