Show MySQL schema collection config

[azhou-datadog]

What does this PR do?

Unhides the mySQL schema collection config, now that schema explorer for mySQL is almost complete.

Motivation

Show customers that they can collect schemas on mySQL

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.03%. Comparing base (1a13d0d) to head (908e078).
Report is 4 commits behind head on master.

Additional details and impacted files

Flag	Coverage Δ
activemq	?
cassandra	?
hive	?
hivemq	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
mysql	89.49% <ø> (?)
presto	?
solr	?

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[azhou-datadog]

/merge

[dd-devflow]

View all feedbacks in Devflow UI.
2025-03-21 15:28:47 UTC ℹ️ Start processing command /merge

---

2025-03-21 15:28:58 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-03-21 16:59:18 UTC ℹ️ MergeQueue: This merge request was already merged

This pull request was merged directly.