feat(span-names): Add url.domainrule for http.client spans

[Lms24]

This PR proposes adding another name generation rule to http.client spans: If we cannot find a parameterized URL matching the first two rules (which is almost always the case in JS at least), we can construct the name based on

{{http.request.method}} {{url.domain}}

to include at least a bit more information than just the method. Would appreciate product input if this is an acceptable level of cardinality!

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• (attributes) Add graphql.processing.type by andreiborza in #572

• (span-names) Add url.domainrule for http.client spans by Lms24 in #575

Bug Fixes 🐛

• (names) Correct graphql span name examples by andreiborza in #573

Internal Changes 🔧

• (attributes) Add search alias for segment name by nsdeschenes in #577

---

_{🤖 This preview updates automatically when you update the PR.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2caaad3. Configure here.}

[mjq]

For completeness: as mentioned in Slack there's a possibility of unlimited cardinality here via subdomains, but I think this is a more useful default, doesn't particularly have infrastructure implications, and users can override the names in an SDK hook if they have a use case with high-cardinality subdomains they'd prefer to be grouped. 👍