fix(dev-env) sync: don't slugify domain if it matches the primary domain

[rinatkhaziev]

Description

In #2081 we've improved handling of network sites that both utilize subdomains and paths (e.g. path.site.test and site.test/path) when syncing from a VIP environment.

Unfortunately, this introduced an unintended consequence where a site's primary domain would be slugified and prepended to the local env root domain. E.g. path.site.test would become path-site-test.vip-local.vipdev.lndo.site

This PR addresses the issue and now the search-replace would follow this logic:

primary_domain => env_slug.vipdev.lndo.site
convenience_domain => env_slug.vipdev.lndo.site
any_other_domain_or_subdomain => slugified_any_other_domain_or_subdomain.env_slug.vipdev.lndo.site`

Paths are handled respectively. E.g. primary_domain/my/site/ => env_slug.vipdev.lndo.site/my/site

Pull request checklist

• Update SETUP.md with any new environmental variables.
• Update the documentation.
• Manually test the relevant changes.
• Follow the pull request checklist
• Add/update automated tests as needed.

New release checklist

• Automated tests pass.
• The Preparing for release checklist is completed.

Steps to Test

Outline the steps to test and verify the PR here.

Example:

1. Check out PR.
2. Run npm run build
3. Run ./dist/bin/vip-cookies.js nom
4. Verify cookies are delicious.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud