Add optional prometheus pod monitor

[alaturqua]

Added Optional Prometheus Pod Monitor Support

Hey everyone,

I've added a new feature to Trino Helm charts that lets you easily monitor your Trino pods with Prometheus. This is totally optional, so you can turn it on or off as you like. Here's a quick rundown of what's new:

• Turn Monitoring On/Off: You can switch monitoring on or off with monitoring.enabled. Handy if you're trying out different setups.
• Set Up Your Metrics Endpoint: With monitoring.path and monitoring.port, you tell Prometheus where to find the metrics it needs to scrape. This means you can set it up exactly how you like it.
• Control How Often Prometheus Checks for Metrics: Use monitoring.interval and monitoring.scrapeTimeout to control how often Prometheus looks for new metrics and how long it waits. This gives you control over the load and responsiveness of your monitoring setup.
• Decide How Prometheus Handles Labels and Timestamps: The settings monitoring.honorLabels and monitoring.honorTimestamps let you control if Prometheus should use the labels and timestamps from your metrics as they are. This can help with sorting and understanding your data.
• Add Extra Labels to Your Metrics: If you want more detail in your metrics, you can use monitoring.additionalPodTargetLabels to add extra labels from your pods. This is great for when you need to filter your metrics or dig into the details.

I hope this helps make monitoring with Prometheus. Looking forward to your feedback and suggestions!

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Isa.Inalcik.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Isa.Inalcik.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Isa.Inalcik.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[alaturqua]

@cla-bot check

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Isa.Inalcik.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[alaturqua]

@cla-bot check

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Isa.Inalcik.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Isa.Inalcik.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[nineinchnick]

I wonder how we should test this. Should there be a separate job in https://github.com/trinodb/charts/blob/main/.github/workflows/ci-cd.yaml, that would install these requirements? If we won't be testing this, I don't think it should be included in the chart.