RFC: Debug/tracing feature flags

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I can't get conclusive debug output.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I run a command and the debug output reveals root cause of the problem.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

See PR #2697

Proposal

Feature flags:

These flags are not part of the full feature:

• spans: activates tracing spans/events/logs.
• debug: Activate debug level spans targeting app-hyper debugging
• trace: Activate debug and trace level spans targeting hyper internal debugging.
• jaeger: Setup the stack required to consume Hyper trace output in Jaeger

Start by reading PR #2697 alongside this RFC to understand the proposed debugging and tracing feature flags. Then locate how feature flags and tracing are currently defined in the repository and clarify the intended scope and acceptance checks before implementation. Done means the agreed design is implemented and the debug output provides the requested diagnostic detail.