Domain dependency version constraint causes unresolved dependency error with Domain 2.x

Problem/Motivation

The dependency declaration in `country_path.info.yml` causes an unresolved dependency error when using Domain 2.x:

dependencies:
  - domain:domain (>=8.x-1.0-beta7)

While `composer.json` correctly supports both Domain 1.x and 2.x:

"drupal/domain": "^1.0.0-beta7 || ^2"

When Domain 2.x (e.g., 2.0.0-beta6) is installed, Drupal's dependency checker reports an unresolved dependency error because the constraint `>=8.x-1.0-beta7` does not recognize 2.x versions as satisfying the requirement, even though they are functionally compatible and allowed by composer.json.

Error message:

Unresolved dependency
Domain (Version >=8.x-1.0-beta7 required)
Country Path requires this module and version. Currently version of Domain is being used.

Steps to reproduce

1. Install Drupal 10
2. Install Domain module version 2.0.0-beta6 (or any 2.x version) via Composer
3. Install Country Path module version 1.9.0 via Composer
4. Enable the Country Path module
5. Navigate to the Status Report page (/admin/reports/status)
6. Observe the unresolved dependency error message

Proposed resolution

Remove the version constraint from `country_path.info.yml` to align with `composer.json`:

dependencies:
  - domain:domain

This allows Composer to manage version requirements while eliminating the dependency mismatch error on the Status Report page.

Remaining tasks

1. Review and apply the patch
2. Test with both Domain 1.x and 2.x versions
3. Commit the fix
4. Create a new release

User interface changes

The unresolved dependency error on the Status Report page will no longer appear when using Domain 2.x with Country Path.

API changes

None.

Data model changes

None.