Fix package.json dependency issues

[darthtrevino]

When using Yarn v2, packages that are explicitly imported within a package scope need to be marked as either a direct dependency or a peer. This prevents tacit module resolution from creeping into dependencies.

1: Move @opentelemetry/semantic-conventions to dependencies.

Justification: it's directly imported in the following locations:

• ApplicationInsights-node.js/AutoCollection/diagnostic-channel/SpanParser.ts

  Line 4 in ec12907

  import { SemanticAttributes, DbSystemValues } from "@opentelemetry/semantic-conventions";

• ApplicationInsights-node.js/AutoCollection/diagnostic-channel/Azure/EventHub.ts

  Line 5 in ec12907

  import { SemanticAttributes } from "@opentelemetry/semantic-conventions";

2: Add @opentelemetry/core to dependencies

Justification it's directly imported in the following location:

• ApplicationInsights-node.js/AutoCollection/diagnostic-channel/Azure/EventHub.ts

  Line 4 in ec12907

  import { hrTimeToMilliseconds } from "@opentelemetry/core";

3: Mark applicationinsights-native-metrics as an optional peer dependency.

Justification: it's conditionally imported in the following location:

ApplicationInsights-node.js/AutoCollection/NativePerformance.ts

Line 63 in ec12907

const NativeMetricsEmitters = require("applicationinsights-native-metrics");

This can be resolved on the client-side, but clients have to monkey-patch in proper dependencies: https://github.com/microsoft/community-organization-operations-suite/blob/b04c9fe9bec52aba50f50ac68a90e398ab620a56/.yarnrc.yml#L45-L48

[hectorhdzg]

Thanks for the contribution