fix(deps): update dependency @vercel/otel to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vercel/otel	^1.14.0 -> ^2.1.0

---

Release Notes

vercel/otel (@​vercel/otel)

v2.1.0

Compare Source

Minor Changes

• #​181 14f773c Thanks @​dvoytenko! - Ignore auto-configuration based on the OTEL_EXPORTER_OTLP_ env vars when trace drains are used. This avoids duplicate trace export.

v2.0.1

Compare Source

Patch Changes

• #​170 9a695ad Thanks @​kakadiadarpan! - add project id to resource attributes

v2.0.0

Compare Source

Major Changes

• #​165 7887411 Thanks @​bengigone! - Add support for OTel JS SDK 2.X

Breaking Changes

1. OpenTelemetry SDK dependencies updated

**API package** (minimum version bumped):

-   `@opentelemetry/api`: `>=1.9.0 <3.0.0` (was `>=1.7.0 <2.0.0`)

**Stable packages** (updated to v2.x):

-   `@opentelemetry/resources`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`)
-   `@opentelemetry/sdk-metrics`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`)
-   `@opentelemetry/sdk-trace-base`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`)

**Experimental packages** (updated to v0.2XX):

-   `@opentelemetry/api-logs`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`)
-   `@opentelemetry/instrumentation`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`)
-   `@opentelemetry/sdk-logs`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`)

2. Minimum Node.js version requirement

The minimum supported Node.js has been raised to `^18.19.0 || >=20.6.0` to align with OpenTelemetry JS SDK 2.x requirements. This means that support for Node.js 14 and 16 has been dropped.

3. Configuration changes

**Log Record Processors:**

```typescript
// Before (v1.x)
registerOTel({
  serviceName: "your-service-name",
  logRecordProcessor: myProcessor, // Single processor
});

// After (v2.x)
registerOTel({
  serviceName: "your-service-name",
  logRecordProcessors: [myProcessor], // Array of processors
});
```

**Metric Readers:**

```typescript
// Before (v1.x)
registerOTel({
  serviceName: "your-service-name",
  metricReader: myReader, // Single reader
});

// After (v2.x)
registerOTel({
  serviceName: "your-service-name",
  metricReaders: [myReader], // Array of readers
});
```

Migration Guide

1.  **Update OpenTelemetry dependencies**: Update the OpenTelemetry packages you are using in your project to the compatible versions:

    **API package** (minimum version bumped):

    ```bash
    npm install @​opentelemetry/api@^1.9.0
    ```

    **Stable packages** (upgrade to v2.x):

    ```bash
    npm install @​opentelemetry/resources@^2.1.0 @​opentelemetry/sdk-trace-base@^2.1.0 @​opentelemetry/sdk-metrics@^2.1.0
    ```

    **Experimental packages** (upgrade to v0.2XX):

    ```bash
    npm install @​opentelemetry/sdk-logs@^0.205.0 @​opentelemetry/instrumentation@^0.205.0 @​opentelemetry/api-logs@^0.205.0
    ```

    **Note**: Only install the packages you are actually using in your project.

2.  **Update configuration**:

    **Log Record Processors** - Change `logRecordProcessor` to `logRecordProcessors`:

    ```typescript
    // Before
    registerOTel({
      serviceName: 'your-service-name',
      logRecordProcessor: myProcessor // Single processor
    });

    // After
    registerOTel({
      serviceName: 'your-service-name',
      logRecordProcessors: [myProcessor], // Array of processors
    });
    ```

    **Metric Readers** - Change `metricReader` to `metricReaders`:

    ```typescript
    // Before
    registerOTel({
      serviceName: 'your-service-name',
      metricReader: myReader, // Single processor
    });

    // After
    registerOtel({
      serviceName: 'your-service-name',
      metricReaders: [myReader], // Array of processors
    });
    ```

3.  **No code changes needed** for basic usage - the SDK interface remains the same for most common use cases.

For complete details on migrating from OpenTelemetry JS SDK 1.x to 2.x, see the [official OpenTelemetry migration guide](https://redirect.github.com/open-telemetry/opentelemetry-js/blob/v2.0.0/doc/upgrade-to-2.x.md).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.