feat(metrics): More SDK-based logic for transaction name extraction [INGEST-1524]

[jjbayer]

Adds more cases of SDK / tag combinations that should be treated as
high-cardinality transaction names. This was obtained from tests with
real-world data, indicating SDK bugs falling back to raw URLs:

• sentry.python: integrations contains "django" when http.status is
  404
• sentry.javascript.node: integrations contains "Express" when
  http.method is "OPTIONS"
• sentry.javascript.nextjs: all
• sentry.php.laravel: all
• sentry.php.symphony: all

More info on how we found problematic SDK cases can be found in the
Jira ticket. The
SDK bugs were filed separately.

Also in this PR: Add a statsd metric for the extracted transaction name.

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

For changes exposed to the Python package, please add an entry to py/CHANGELOG.md. This includes, but is not limited to event normalization, PII scrubbing, and the protocol.

For changes to the Relay server, please add an entry to CHANGELOG.md under the following heading:

1. Features: For new user-visible functionality.
2. Bug Fixes: For user-visible bug fixes.
3. Internal: For features and bug fixes in internal operation, especially processing mode.

To the changelog entry, please add a link to this PR (consider a more descriptive message):

- More SDK-based logic for transaction name extraction. ([#1356](https://github.com/getsentry/relay/pull/1356))

If none of the above apply, you can opt out by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against efe0382