feat: manual image rebuild trigger

[MacMur85]

Description

This PR includes a modification to a stage-3-build-images.yaml workflow and a get-docker-names.sh script for us to be able to run a manual image rebuilding process.

Context

A manual rebuilding process is needed to be able to:

1. Re-run a failed job which was supposed to create new image versions after a code merge to the main branch.
2. Test changes in the CI process itself without the need to wait for a code merge.

The proposed solution consists of:

1. A modification to the stage-3-build-images.yaml, which will have two alternative executing methods:

• the default automatic one (no changes to the process)
• a manual one, which will be triggered from the GitHub Actions Portal and will always result in rebuilding all images using the code from the current main branch

2. A modification to the get-docker-names.sh, which will have another parameter passed in by the workflow (MANUAL_BUILD_ALL).

• for MANUAL_BUILD_ALL = false the script will work the same as before
• for MANUAL_BUILD_ALL = true the script will no longer look for changes in the code, and will always return a full list of functions to rebuild (input needed by the workflow)

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.