Upgrading composer to specific Drupal version 9.4.10

Until now we built the image with latest patch version (as per https://semver.org/), therefore the same pipeline executed in two different periods would result in different patch versions.

I'm not sure if it is to be kept or not, but as per the last run, we are serving Drupal core 9.4.8 which does not contain latest security patch. As per docs, I've executed commands to have the latest version with a specific release.

Expected included changes:

• https://www.drupal.org/project/drupal/releases/9.4.9 (Bug fixes)
• https://www.drupal.org/project/drupal/releases/9.4.10 (Security patch)

If this is to be discarded and just re-run the master branch, please discuss below.

requested review from @crdeoliv, @ravineet, @jyde, and @ldelpian

Note: CI will keep failing for clone, as the source of the clone is the IT website, which is yet not compatible with PHP 8, if there's a more suitable candidate to use for the clone tests of PHP8, please suggest/discuss, as it will increase the confidence of MRs.

In my opinion, it really does not make sense that executing the same pipeline can result in two different patch versions. I understand why this is the case, but it really does not make a lot of sense from the perspective of the users (or ourselves when we are testing!). That said, I have looked at 9.4.9 and 9.4.10, and we should be all good applying these.

approved this merge request

approved this merge request

Agree this change is good, allows better versioning, tracking changes and rollback if needed..

approved this merge request

merged

mentioned in commit c9b66ee1