Refactor GitHub workflows and use composite actions

[ReeceHumphreys]

• Tickets addressed: bsk-1072
• Review: By file
• Merge strategy: Merge (no squash)

Description

This PR aims to simplify and refactor our CI pipeline. By using GitHub actions we can have reusable components in the CI jobs that are easier to reason about and will be useful for automating the deployment of wheels in the future. The goals of this PR were to generally avoid changing CI behavior unless it removed duplication or increased consistency.

Notable changes

• Created .github/actions which contains a reusable build action for bsk and the docs
• Updated pull-request-closed.yml to merge.yml and simplified logic to reflect this is a workflow only intended to run on merges
• Simplified pull-request.yml by using the reusable actions
• Simplified version bump checking
• Gated docs build/deploy behind successful macOS builds

Verification

This PR will trigger workflows to validate the updates. Future commits may be added to resolve issues found during this testing. The PR should be squashed and merged to avoid polluting the git history.

Documentation

N/A

Future work

1. Evaluate which platforms to support, which Python versions to test on each, and whether to include Conan-based installs. This is out of scope for this PR, which focuses only on refactoring and simplifying the existing CI.

2. Update the CI to automatically create and deploy wheels to PyPI for all supported platforms. We currently build and store wheels for ubuntu but do not publish them.

3. Simplify the various requirements.txt files and move them into pyproject.toml per PEP 518 and PEP 621

Closes #1072

[schaubh]

Nice refactor. Just a few comments and a question about including the one new python requirement to BSK requirements, rather than just including it in the CI test builds?

[schaubh]

In notice we have 10 "pending check" where the PR is waiting for the results for the old CI test run names. When this is pushed, I'll have to remember to edit the repo settings to look for these new test run names. Do you have GitHub access privileges to look into this yourself? Obviously not before this branch is pushed.

[schaubh]

love this branch. I really like how you have refactors the CI scripts. Just some very minor items and questions about the commit history. You add some stuff in the first commit, only to un-add it in the 2nd commit. Should be easy to clean up.

Also, when pushed to develop, we'll need to change the GitHub repo settings to make the PR requirements look for these new CI test names.

[ReeceHumphreys]

In notice we have 10 "pending check" where the PR is waiting for the results for the old CI test run names. When this is pushed, I'll have to remember to edit the repo settings to look for these new test run names. Do you have GitHub access privileges to look into this yourself? Obviously not before this branch is pushed.

I don't believe so. I think the only GitHub settings privilege I have is to add new Repository secrets for actions.

[ReeceHumphreys]

Commit 985a42a was updated to add an extra macOS build with the --vizInterface False added to the conan_args.