Break CI Github Action Into Smaller Jobs

[Jdubrick]

What does this PR do / why we need it

This PR breaks apart the large job that was being run as part of our CI workflow and splits it into multiple smaller jobs. This is because we were running into storage problems during some runs. By splitting the larger job into multiple smaller ones we can take advantage of having different environments and thus separate storage constraints for each job.

When working on this PR I initially tried to implement reusable workflows so that the copy-paste of the checkout, setup, sha, and install steps did not need to be duplicated for each job. However, since each job is a new virtual environment it is unable to run the rest of the job without those steps also being present and run within them.

Additionally, in order for nx to allow my push to go through it was requiring me to rename ci.yml to ci.yaml, this may be a format setting that is defined as part of nx cloud that I do not have access to. I am assuming this because I found nothing in the repo that suggests a naming convention for yaml files, only through nx docs stating that .yaml is the preferred.

Which issue(s) does this PR fix

Fixes devfile/api#1464

PR acceptance criteria

• Unit Tests
• E2E Tests
• Documentation
  Update the sidebar if there is a new file added or an existing filename is changed

How to test changes / Special notes to the reviewer

[michael-valdron]

Aside from my comment and the feedback from code scanning, we'll need to remove the required constraint from the removed Main Job:

FYI @elsony

[Jdubrick]

Added top level permission so token can only read for the CI job as it was being flagged by the scorecard. Additionally pinned the version of setup-node and nx-set-shas to v4.0.0 for each, an upgrade in version from what they previously were at as they were severely outdated.

[michael-valdron]

/lgtm

PR changes looks good, just need the branch protection changed to remove the old job.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jdubrick, michael-valdron

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Jdubrick,michael-valdron]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[michael-valdron]

just need the branch protection changed to remove the old job

Fixed.

FYI @Jdubrick