Y25-099 - Migrate & Improve GitHub Actions - Sequencescape

[SHIV5T3R]

Describe the Housekeeping
As a part of the parent story, the workflows for Sequencescape can be migrated to shared workflows and improved upon.

Workflows to migrate

• append_release.yml - This should be a shared workflow, it is also used in Limber.
• automated_docker_release.yml - SHOULD be migrated, it is only used here - see additional context.
• automated_release.yml - This needs to use a shared workflow, it will be made because other repositories use this too.
• check_docker_build.yml - This workflow and check is only used here. It COULD be worth migrating this to a shared workflow, but none of the other main apps use docker.
• check_release_version.yml - Use the shared workflow version of this, it's used everywhere.
• generate_pages.yml - Docs are generated in other repo, but it works differently. This can be left.

---

See additional context

• js_test.yml - Runs yarn test
• lint.yml - Runs yarn lint and rubocop
• lint_yard_docs.yml - Runs linting for yard docs
• ruby_test.yml - Runs rspec and cucumber tests.. Opportunity to consolidate/make this more readable
• update_rubocop.yml - Updates rubocop rules (?).. Limber uses this, but the workflows have a slightly different name. This should be migrated to a shared workflow.

Potential improvements
Setup any environments (node/bundle) an cache them. These cached instances can then be used, being relied on by each step, so that the instance is only created once.

Related issues

• Y24-510 - Migrate GitHub actions to shared workflows General-Backlog-Items#479

Additional context
Sequencescape uses docker containers, so when there is a new release, a new docker image is made. We do use this functionality across the organisation, but it's in workflows with different names, sometimes with other actions merged with it. This docker image functionality should be migrated into a shared workflow so that it can be used in other repositories, and also remain as modular as possible.

For the second set of workflows, they can be split by their respective environments and the environment setup can be done once for each.