FW-147 Change skynet config to check that github workflow passes

[wesleybalvanz-wf]

Motivation

Currently skynet is running the same tests as github workflows instead lets just check and see if github workflows passes or not in skynet.

Changes

Changed skynet config to verify github workflow is successful instead of running the tests in both places.

Release Notes

Change skynet config to verify github workflow is successful.

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

[aviary2-wf]

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.

[evanweible-wf]

QA +1

• CI passes

[evanweible-wf]

QA +1
@Workiva/release-management-p

[evanweible-wf]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM