[monitor] Update to latest @opentelementry packages (Azure#26204)

### Packages impacted by this PR

- @azure/opentelemetry-instrumentation-azure-sdk
- @azure/monitor-opentelemetry-exporter
- @azure/monitor-opentelemetry
- @azure/monitor-query

### Issues associated with this PR

- Azure#26173
- Azure#26172

### Describe the problem that is addressed by this PR

Updates to latest OTEL packages across the board.

### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?


### Are there test cases added in this PR? _(If not, why?)_


### Provide a list of related PRs _(if any)_


### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)

Author: mpodwysocki

common/config/rush/pnpm-lock.yaml

@@ -80,17 +80,17 @@
     "@azure/core-tracing": "^1.0.0",
     "@azure/logger": "^1.0.0",
     "@opentelemetry/api": "^1.4.1",
-    "@opentelemetry/core": "^1.13.0",
-    "@opentelemetry/instrumentation": "^0.39.0",
+    "@opentelemetry/core": "^1.14.0",
+    "@opentelemetry/instrumentation": "^0.40.0",
     "tslib": "^2.2.0"
   },
   "devDependencies": {
     "@azure/core-rest-pipeline": "^1.5.1",
     "@azure/dev-tool": "^1.0.0",
     "@azure/eslint-plugin-azure-sdk": "^3.0.0",
     "@microsoft/api-extractor": "^7.31.1",
-    "@opentelemetry/sdk-trace-base": "^1.13.0",
-    "@opentelemetry/sdk-trace-node": "^1.13.0",
+    "@opentelemetry/sdk-trace-base": "^1.14.0",
+    "@opentelemetry/sdk-trace-node": "^1.14.0",
     "@types/chai": "^4.1.6",
     "@types/mocha": "^7.0.2",
     "@types/node": "^14.0.0",

sdk/instrumentation/opentelemetry-instrumentation-azure-sdk/package.json

@@ -108,13 +108,13 @@
     "@azure/core-auth": "^1.3.0",
     "@azure/core-rest-pipeline": "^1.1.0",
     "@opentelemetry/api": "^1.4.1",
-    "@opentelemetry/api-logs": "0.39.1",
-    "@opentelemetry/core": "^1.13.0",
-    "@opentelemetry/resources": "^1.13.0",
-    "@opentelemetry/sdk-metrics": "^1.13.0",
-    "@opentelemetry/sdk-trace-base": "^1.13.0",
-    "@opentelemetry/semantic-conventions": "^1.13.0",
-    "@opentelemetry/sdk-logs": "0.39.1",
+    "@opentelemetry/api-logs": "^0.40.0",
+    "@opentelemetry/core": "^1.14.0",
+    "@opentelemetry/resources": "^1.14.0",
+    "@opentelemetry/sdk-metrics": "^1.14.0",
+    "@opentelemetry/sdk-trace-base": "^1.14.0",
+    "@opentelemetry/semantic-conventions": "^1.14.0",
+    "@opentelemetry/sdk-logs": "^0.40.0",
     "tslib": "^2.2.0"
   },
   "sideEffects": false,

sdk/monitor/monitor-opentelemetry-exporter/package.json

@@ -31,12 +31,12 @@
     "@azure/monitor-opentelemetry-exporter": "next",
     "dotenv": "latest",
     "@opentelemetry/api": "^1.4.1",
-    "@opentelemetry/resources": "^1.13.0",
-    "@opentelemetry/semantic-conventions": "^1.13.0",
-    "@opentelemetry/sdk-trace-base": "^1.13.0",
-    "@opentelemetry/instrumentation": "^0.39.0",
-    "@opentelemetry/sdk-trace-node": "^1.13.0",
-    "@opentelemetry/instrumentation-http": "^0.39.0",
-    "@opentelemetry/sdk-metrics": "^1.13.0"
+    "@opentelemetry/resources": "^1.14.0",
+    "@opentelemetry/semantic-conventions": "^1.14.0",
+    "@opentelemetry/sdk-trace-base": "^1.14.0",
+    "@opentelemetry/instrumentation": "^0.40.0",
+    "@opentelemetry/sdk-trace-node": "^1.14.0",
+    "@opentelemetry/instrumentation-http": "^0.40.0",
+    "@opentelemetry/sdk-metrics": "^1.14.0"
   }
 }