feat: added monitoring for postgres query result

[daltonpearson]

Summary

In this pull request, the following changes are made:

• Added monitoring for postgres query results as discussed in Monitor Postgres query result #2342
• Added relevant tests

• Resolves Monitor Postgres query result #2342

Please follow this checklist to avoid unnecessary back and forth (click to expand)

• ⚠️ If there are Breaking change (a fix or feature that alters existing functionality in a way that could cause issues) I have called them out
• 🧠 I have disclosed any use of LLMs/AI in this contribution and reviewed all generated content.
  I understand that I am responsible for and able to explain every line of code I submit.
• 🔍 Any UI changes adhere to visual style of this project.
• 🛠️ I have self-reviewed and self-tested my code to ensure it works as expected.
• 📝 I have commented my code, especially in hard-to-understand areas (e.g., using JSDoc for methods).
• 🤖 I added or updated automated tests where appropriate.
• 📄 Documentation updates are included (if applicable).
• 🧰 Dependency updates are listed and explained.
• ⚠️ CI passes and is green.

Screenshots for Visual Changes

• UI Modifications: Highlight any changes made to the user interface.

[CommanderStorm]

Looks very much like the code in the other db-like monitors 👍🏻

Thanks for implementing this and adding the testcases!

[louislam]

#6794 should be broken by this.

Is it an AI pull request? Is it really tested?

I am planning to release 2.1.0 soon. The test file probably doesn't cover all cases. If no one test on Postgres manually, it will be reverted.

[CommanderStorm]

@louislam let's revert it and put the change into 2.2.
I did not manually test since the tests seemed solid.

[daltonpearson]

Sorry I’m on vacation currently, I did test that case I thought so I’m confused as to why it’s broken. I’ll take a look next week when I get back, sorry about that.

[daltonpearson]

So when testing locally on my branch and on 3.0.X(baaf14c) I get the expected behavior with "SELECT 1" as well as an empty query field with no conditions returns an "UP" status. Investigating further.