On-Hold Closes #2612 Upgrade cweagans/composer-patches to version 2

[trackleft]

Description

This PR upgrades the cweagans/composer-patches package to version 2. This update is necessary to maintain compatibility with the latest composer updates and ensure our patching workflow remains efficient and reliable. The upgrade process involved updating the composer.json file and ensuring all existing patches are still applied correctly.

Related issues

Closes #2612

This PR is blocked by two other PRs:

• Closes #3191 Remove patch for drupal.org/i/3163925 #3193
• Close #3192 Update patch for drupal.org/i/2552541 #3194

How to test

1. Check out this PR.
2. Run composer update cweagans/composer-patches.
3. Ensure all patches defined in composer.json are applied without errors.
4. Test the functionality that relies on patched packages to verify there are no regressions.

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[joeparsons]

Might require changes in these other repos as well...

https://github.com/az-digital/az-quickstart-scaffolding/blob/main/composer.json#L32
https://github.com/az-digital/az-quickstart-scaffolding/blob/main/composer.json#L85-L89

https://github.com/az-digital/az-quickstart-pantheon/blob/master/upstream/composer.json#L15
https://github.com/az-digital/az-quickstart-pantheon/blob/master/composer.json#L44-L45
https://github.com/az-digital/az-quickstart-pantheon/blob/master/composer.json#L66-L68

[trackleft]

Blocked by #3191
Blocked by #3192

[joeparsons]

Definitely glad to see this working.

Question: should we wait until a stable release is available before upgrading to 2.x?

[trackleft]

Need to update the google tag patch.

1027
1028In Patches.php line 288:
1029                                                                               
1030  No available patcher was able to apply patch https://www.drupal.org/files/i  
1031  ssues/2024-03-01/3424623-9-allow-saving-google-tag-setting-for-consent-mode  
1032  .patch to drupal/google_tag                                                  
1033