chore: Update the express example

[sp6370]

Which problem is this PR solving?

• Updates to the express example Update examples and only use Console Exporters #2528

Short description of the changes

• Nukes the Zipkin usage and usage of Jaeger Otel Library
• Added a fix for the code compilation failing
• Update the otel dependencies to latest version
• Also fix the deprecations for the semantic conventions

[sp6370]

@trentm Thanks a lot for your help and feedback on the PR. Looking forward to the code review! 😄

[trentm]

Some notes. Looking good, thanks.

[trentm]

Suggested change

	OpenTelemetry Express Instrumentation allows the user to automatically collect trace data and export them to the backend of choice (we can Jaeger for this example), to give observability to distributed systems.
	OpenTelemetry Express Instrumentation allows the user to automatically collect trace data and export them to the backend of choice (we use Jaeger for this example), to give observability to distributed systems.

[trentm]

Suggested change

	### Jaeger
	Run the server:
	Run the server:

Now that the example only uses Jaeger, I think the subsection title can be dropped.

[trentm]

What do you think about dropping the jaeger: prefix on these now that there is just the one target? I think it is less confusing to the user to npm run server.

Suggested change

	"jaeger:server": "cross-env EXPORTER=jaeger ts-node src/server.ts",
	"jaeger:client": "cross-env EXPORTER=jaeger ts-node src/client.ts",
	"server": "ts-node src/server.ts",
	"client": "ts-node src/client.ts",

The EXPORTER envvar is no longer necessary, and then cross-env is no longer necessary.

If you agree, please also:

• run: npm uninstall cross-env
• update the npm run ... commands in README.md

[trentm]

This coiuld be simplified to just use OTLPTraceExporter below.

Suggested change

const Exporter = OTLPTraceExporter;

[trentm]

Suggested change

	const exporter = new Exporter({});
	const exporter = new OTLPTraceExporter();

[trentm]

I think it would be okay to repeat the one-liner to start Jaeger. Something like:

Suggested change

	Setup [Jaeger Tracing](https://www.jaegertracing.io/docs/2.0/getting-started/#in-docker)
	Start Jaeger in Docker for receiving tracing data (see [the Jaeger docs](https://www.jaegertracing.io/docs/2.0/getting-started/#in-docker) for more details in running Jaeger):
	```bash
	docker run --rm --name jaeger \
	-p 5778:5778 \
	-p 16686:16686 \
	-p 4317:4317 \
	-p 4318:4318 \
	-p 14250:14250 \
	-p 14268:14268 \
	-p 9411:9411 \
	jaegertracing/jaeger:2.0.0 \
	--set receivers.otlp.protocols.http.endpoint=0.0.0.0:4318 \
	--set receivers.otlp.protocols.grpc.endpoint=0.0.0.0:4317
	```

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.75%. Comparing base (5eb61d8) to head (0baefbc).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2532   +/-   ##
=======================================
  Coverage   90.75%   90.75%           
=======================================
  Files         169      169           
  Lines        8018     8018           
  Branches     1632     1632           
=======================================
  Hits         7277     7277           
  Misses        741      741           

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles