neat(logs) prefer to use Sentry.logger over const { logger } (#15743)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
* Update to `Sentry.logger` from `const { logger } = Sentry` in AI docs
for logs

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

Author: sergical

platform-includes/llm-rules-platform/_default.mdx

@@ -79,7 +79,7 @@ async function fetchUserData(userId) {
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/browser"`
 - Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
-- Reference the logger using `const { logger } = Sentry`
+- Reference the logger using `Sentry.logger`
 - Sentry offers a `consoleLoggingIntegration` that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
 ## Configuration
@@ -110,25 +110,23 @@ Sentry.init({
 
 ## Logger Examples
 
-`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
+`Sentry.logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
 
 ```javascript
 import * as Sentry from "@sentry/browser";
 
-const { logger } = Sentry;
-
-logger.trace("Starting database connection", { database: "users" });
-logger.debug(logger.fmt`Cache miss for user: ${userId}`);
-logger.info("Updated profile", { profileId: 345 });
-logger.warn("Rate limit reached for endpoint", {
+Sentry.logger.trace("Starting database connection", { database: "users" });
+Sentry.logger.debug(Sentry.logger.fmt`Cache miss for user: ${userId}`);
+Sentry.logger.info("Updated profile", { profileId: 345 });
+Sentry.logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",
   isEnterprise: false,
 });
-logger.error("Failed to process payment", {
+Sentry.logger.error("Failed to process payment", {
   orderId: "order_123",
   amount: 99.99,
 });
-logger.fatal("Database connection pool exhausted", {
+Sentry.logger.fatal("Database connection pool exhausted", {
   database: "users",
   activeConnections: 100,
 });

platform-includes/llm-rules-platform/javascript.nextjs.mdx

@@ -79,7 +79,7 @@ async function fetchUserData(userId) {
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/nextjs"`
 - Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
-- Reference the logger using `const { logger } = Sentry`
+- Reference the logger using `Sentry.logger`
 - Sentry offers a consoleLoggingIntegration that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
 ## Configuration

platform-includes/llm-rules-platform/javascript.node.mdx

@@ -74,7 +74,7 @@ async function fetchUserData(userId) {
 
 - Where logs are used, ensure they are imported using `import * as Sentry from "@sentry/node"`
 - Enable logging in Sentry using `Sentry.init({ enableLogs: true, })`
-- Reference the logger using `const { logger } = Sentry`
+- Reference the logger using `Sentry.logger`
 - Sentry offers a consoleLoggingIntegration that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
 ## Configuration

platform-includes/llm-rules-platform/javascript.react.mdx

@@ -74,7 +74,7 @@ async function fetchUserData(userId) {
 
 - Where logs are used, ensure Sentry is imported using `import * as Sentry from "@sentry/react"`
 - Enable logging in Sentry using `Sentry.init({ enableLogs: true })`
-- Reference the logger using `const { logger } = Sentry`
+- Reference the logger using `Sentry.logger`
 - Sentry offers a consoleLoggingIntegration that can be used to log specific console error types automatically without instrumenting the individual logger calls
 
 ## Configuration