Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

refactor(matchers): review cleanups

Lower-severity items from the topic-matcher review:

- Reject a publish "data" field that is not valid UTF-8 (400), matching the
  protocol's UTF-8 requirement that ParseForm does not enforce.
- Iterate subscribe query parameters in sorted order so the resulting matcher
  order (observable in subscription IDs, the subscription API and span
  attributes) is deterministic instead of depending on Go map iteration order.
- Drop the dead maxQueryTopics constant (the subscribe path is capped by
  maxMatcherCount) and point the test at the enforced limit.
- Remove the unreachable deprecatedMatcherTypeName case in matcherTypeFromParam
  (the internal type is not addressable from the wire; default already rejects
  it).