Switch to a local patching system using vardot/varbase-patches and cweagans/composer-patches ~2 within Varbase Reports

Problem/Motivation

cweagans/composer-patches 2.0.0-beta1 was released
https://github.com/cweagans/composer-patches/releases/tag/2.0.0-beta1
cweagans/composer-patches 2.0.0-beta2 was released
https://github.com/cweagans/composer-patches/releases/tag/2.0.0-beta2

Many improvements for the patching system.

Proposed resolution

• Switch to vardot/varbase-patches
• Update cweagans/composer-patches to ~2
• Pave the way for a smooth update for the patching system.

Remaining tasks

• ✅ File an issue about this project
• ✅ Addition/Change/Update/Fix to this project
• ✅ Testing to ensure no regression
• ✅ Automated unit/functional testing coverage
  • Varbase 10.0.x
  • Varbase 9.1.x
• ✅ Developer Documentation support on feature change/addition
  
  Added to Varbase Docs

  • Varbase Patches
  • Managing Only Local Patches for Projects
  • Storage of Local Patches Branch
  • Examples of Names for Local Patch files
  • Why Direct Links for Merge Requests Aren't Preferred
  • Handling Varbase Patches Ignoring
• ➖ User Guide Documentation support on feature change/addition
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ✅ Code review from 1 Varbase core team member
• ✅ Full testing and approval
• ✅ Credit contributors
• ✅ Review with the product owner
• ✅ Update Release Notes and Update Helper on new feature change/addition
• ✅ Release varbase-10.0.0-rc2, varbase_reports-10.0.1

Varbase update type

• ✅ No Update
• ➖ Optional Update
• ➖ Forced Update
• ➖ Forced Update if Unchanged

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• Issue #3437241: Switched to a local patching system using vardot/varbase-patches and cweagans/composer-patches "~2" within Varbase Reports