[Draft]: Disable Monitoring console test cases for now for test analysis

[vivekr-splunk]

Description

What does this PR have in it?

Key Changes

Highlight the updates in specific files

Testing and Verification

How did you test these changes? What automated tests are added?

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

• Code changes adhere to the project's coding standards.
• Relevant unit and integration tests are included.
• Documentation has been updated accordingly.
• All tests pass locally.
• The PR description follows the project's guidelines.

[github-actions]

CLA Assistant Lite bot: All contributors have NOT signed the COC Document

---

I have read the Code of Conduct and I hereby accept the Terms

---

vivek.name: "Vivek Reddy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request}

[coveralls]

Pull Request Test Coverage Report for Build 21525804711

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 86.573%

---

Totals
Change from base Build 21255354690:	0.0%
Covered Lines:	10710
Relevant Lines:	12371

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 21525804740

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.008%) to 86.565%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/splunk/enterprise/afwscheduler.go	1	92.9%

Totals
Change from base Build 21255354690:	-0.008%
Covered Lines:	10709
Relevant Lines:	12371

---

💛 - Coveralls

[kasiakoziol]

Why do you comment out these pieces of code and why do you try to push it directly to main?

[vivekr-splunk]

Why do you comment out these pieces of code and why do you try to push it directly to main?
This change was done to analyze how the tests behave without the MC tests enabled. MC should not be part of all test cases - we already have dedicated MC-specific tests for that. The MC tests are currently flaky, and when they fail they often produce misleading errors that obscure failures in unrelated tests.
My goal was to temporarily disable MC in the other tests and keep it only in the MC-related test cases to get clearer signal from the rest of the suite.
That said, please ignore this PR. It is in draft mode and was never intended to be merged anywhere.