add legacy mode to jaeger tracing exporter to support 128bit trace ids

[Jank1310]

…32 digits) trace ids

📝 Description

Add support for the 128bit trace ids to be compatible with opentelemetry

Trace context: https://www.w3.org/TR/trace-context/#trace-id
Jaeger FAQ: https://www.jaegertracing.io/docs/2.0/faq/

🎯 Relevant issues

#1311

💎 Type of change

• This change requires a documentation update

📜 Example code

tracing: {
  enabled: true,
  exporter: {
    type: "Jaeger",
    options: {
    legacyMode: false
    }
  }
}

🚦 How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Unit Tests
• Manual test with local otel collector:

Output from otel debug exporter

Span #1
    Trace ID       : adf6f571b8324c6eb6f65b64b4562450
    Parent ID      :
    ID             : adf6f571b8324c6e
    Name           : action 'math.add'
    Kind           : Server
    Start time     : 2025-01-06 15:28:15.496 +0000 UTC
    End time       : 2025-01-06 15:28:15.496943 +0000 UTC
    Status code    : Unset
    Status message :

🏁 Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/moleculerjs/moleculer@1314

commit: a1419d8

[Jank1310]

@icebob Any idea ho to fix the pipeline?

[icebob]

I have no idea, the memwatch dep can't build itself on older Node versions. But it's not a mandatory dependency, I'm removing it...

[icebob]

I've fixed it in the master workflows, could you pull the commits from master into your fork, please?