[build] Chore/optimize build for pull request

[Michaelpalacce]

Description

Main point of this is to stop the limit or whatever we are hitting due to running many mnay jobs at the same time for each commit.

Build:

• Will be triggered on opened PRs as well as forks
• Will be triggered for main, so main will still be build
• Normal Pushes will not trigger as that double builds the project
• If you don't have a PR, you don't get a build

Linter + CodeQL

• Only makes sense during PR

Checklist

• [x] I have added relevant error handling and logging messages to help troubleshooting
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] I have added necessary documentation, relevant usage information (if applicable)
• [x] I have updated the PR title with affected component, related issue number and a short summary of the changes introduced
• [x] I have added labels for implementation kind (kind/) and version type (version/)
• [x] I have tested against live environment, if applicable
• [x] I have synced any structure and/or content vRA-NG improvements with vra-ng and ts-vra-ng archetypes (if applicable)
• [x] I have my changes rebased and squashed to the minimal number of relevant commits. Notice: don't squash all commits
• [x] I have added a descriptive commit message with a short title, including a Fixed #XXX - or Closed #XXX - prefix to auto-close the issue

[vmwclabot]

@Michaelpalacce, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 3295011ef1644f0b6371ef08fbc2b6154f943ff6 must be signed by stefan.genov@broadcom.com

[vmwclabot]

@Michaelpalacce, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 3295011ef1644f0b6371ef08fbc2b6154f943ff6 must be signed by stefan.genov@broadcom.com

[vmwclabot]

@Michaelpalacce, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 3295011ef1644f0b6371ef08fbc2b6154f943ff6 must be signed by stefan.genov@broadcom.com
• Commit 3f047833b5c8a1026adf31f217a91ad16149d959 must be signed by stefan.genov@broadcom.com

[vmwclabot]

@Michaelpalacce, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 3295011ef1644f0b6371ef08fbc2b6154f943ff6 must be signed by stefan.genov@broadcom.com
• Commit 3f047833b5c8a1026adf31f217a91ad16149d959 must be signed by stefan.genov@broadcom.com