Move Tracing project setting model to Core [RUN AS-IF-FOSS]

What does this MR do?

This MR moves Project Setting for Tracing from Enterprise Edition to GitLab Core as a part of #42645 (closed).

Note, this MR does not contain user-facing changes hence the missing changelog entry.

Potential refactorings are tracked in #259282 (closed).

Story

1. Move Tracing project setting model to Core - !43869 (merged)
2. Move Tracing usage data ping to Core - !44006 (merged)
3. Move Tracing operations service to Core - !44303 (merged)
4. Move Tracing operations controller to Core - !44323 (merged)
5. Move Tracing controller to Core - !44604 (merged)
6. Move remaining parts of Tracing to Core - !44574 (merged)
7. Follow-up refactorings and tasks - #259282 (closed)

Screenshots

	GitLab Core (with FOSS_ONLY=1)	Enterprise Edition with GitLab Premium ✔	Enterprise Edition without GitLab Premium 🚫
Operations > Tracing disabled
Operations > Tracing enabled
Settings > Operations > Jaeger tracing disabled
Settings > Operations > Jaeger tracing enabled

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team