feat: Align sentry origin with documentation

[JPeer264]

There were 2 major changes:

• auto.console.logging -> auto.log.console
• auto.logging.* -> auto.log.*

This can go in already, I am just not sure if this should be a breaking change or a minor bump, since theoretically dashboards or bookmarked searches/groupings would be failing.

(closes #17900)

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	8,839	-	8,670	+2%
GET With Sentry	1,328	15%	1,343	-1%
GET With Sentry (error only)	5,953	67%	6,020	-1%
POST Baseline	1,183	-	1,173	+1%
POST With Sentry	496	42%	499	-1%
POST With Sentry (error only)	1,047	89%	1,047	-
MYSQL Baseline	3,240	-	3,280	-1%
MYSQL With Sentry	407	13%	425	-4%
MYSQL With Sentry (error only)	2,641	82%	2,670	-1%

View base workflow run

[AbhiPrasad]

Technically this is a breaking change, but I think we are fine to merge this in as the behaviour is more correct.

It is very unlikely that users will be relying on this value for dashboards/alerts, but we can always ask a product team (like telemetry experience) to do a redash query to check.