Improve domain_match Function and add test cases

[theodesp]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.

Description

This PR enhances the domain_match function to handle a wider range of scenarios, including different ports, schemes, and subdomains. It also adds a comprehensive set of test cases to ensure the function behaves correctly in various situations.

Related Issue(s):

(#1884)

Testing

1. Create a front end Node environment runs on localhost:3000, and LocalWP environment runs on localhost with a different port.
2. Run the development server using npm run dev -w examples/next/faustwp-getting-started
3. The CLI tool should not fail the health check for WordPress URL validation.

Screenshots

Alternatively if you can also try create a new front end Node environment with the same host as the LocalWP environment but in a different port.

Documentation Changes

Dependant PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: a48a338

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@faustwp/wordpress-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[ChrisWiegman]

LGTM