Update Tagify module from ~1 to ~2

Problem/Motivation

Varbase Content Base recipe allows "drupal/tagify": "~1.0 || ~2.0". Since vardot/varbase-patches 11.0.48 switched to the Tagify 2.x patch, Varbase 11 builds that still resolve Tagify 1.x fail at patching.

Moving every Varbase consumer to ~2.0 keeps one Tagify patch for all lines. See Vardot/varbase-patches#662.

Steps to reproduce

1. Build Varbase 11 with vardot/varbase-patches 11.0.48 or later, where Composer resolves drupal/tagify 1.x.
2. The Tagify 2.x patch does not apply to Tagify 1.x and the build fails at patching.

Proposed resolution

Require "drupal/tagify": "~2.0" in composer.json. Tagify 2.0.5 supports Drupal ^10.3 || ^11 || ^12.

Remaining tasks

• ✅ File an issue
• ❌ Addition/Change/Update/Fix
• ❌ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Developer Documentation support
• ➖ User Guide Documentation support
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Reviewed by a human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ✅ Update Release Notes
• ✅ Release Varbase Content Base 1.0.4

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• Requires Tagify 2 (drupal/tagify: ~2.0).