docs: Update broken link to Otel JS Getting Started (#1302)

To reflect the change of location [upstream]

[upstream]: open-telemetry/opentelemetry-js#2493

docs/source/opentelemetry.mdx

@@ -208,7 +208,7 @@ Our example telemetry configuration assumes that Zipkin is running locally, and
 
 To prepare for production, we probably at least want to conditionally set the `url` option for the `ZipkinExporter` and replace our `SimpleSpanProcessor` with a  `BatchSpanProcessor`.
 
-You can learn more about the settings available to these and other OpenTelemetry objects in the [getting started guide](https://github.com/open-telemetry/opentelemetry-js/tree/main/getting-started).
+You can learn more about the settings available to these and other OpenTelemetry objects in the [getting started guide](https://opentelemetry.io/docs/instrumentation/js/getting-started/).
 
 ## GraphQL-specific spans