Decouple Acquia CMS Image from Common Module and Modernize CI Pipeline

Problem/Motivation

The current implementation of the Acquia CMS Image module includes a dependency on the Acquia CMS Common module. So, installing Acquia CMS Image module installs Acquia CMS Common module, which in turn brings in several additional modules that are not necessary for Acquia CMS Image to function. To streamline dependencies, we should remove the reliance on Acquia CMS Common and instead declare only the modules directly required by Acquia CMS Image (e.g., Field Group).

Proposed resolution

1. Review and limit module dependencies so that only modules essential to Acquia CMS Image remain enabled.
2. Update the GitLab CI template and use CI template provided by Drupal Core, replacing the current ORCA setup, and remove any files specific to ORCA.
3. Add / Update code in Acquia CMS Image module for module to function as expected.
4. Refactor and update PHPUnit tests to ensure they are passing.
5. Ensure all CI pipelines complete successfully, including those in the "allowed failures" category.