feat(scaler): Add TLS support for Artemis scaler

[chiragbhatia8]

Description

This PR introduces TLS support for the Artemis scaler, allowing secure communication with Artemis brokers.

Checklist

• When introducing a new scaler, I agree with the scaling governance policy
• I have verified that my change is according to the deprecations & breaking changes policy
• Tests have been added
• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• Changelog has not been updated and is aligned with our changelog requirements
• A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
• A PR is opened to update the documentation on (repo) (if applicable)

Related Issues and PRs

Fixes #6448

---

Notes

This PR includes:

• TLS configuration support (CA, Cert, Key) for Artemis scaler.
• Updated unit tests and metadata validation.

Testing TLS functionality directly in an e2e environment might require additional configuration.

[semgrep-app]

Semgrep found a possible database connection string built with string concatenation. Check for proper encoding/escaping of components to prevent parse errors and injection vulnerabilities.

_{Ignore this finding from db-connection-string.}

[semgrep-app]

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.

_{Ignore this finding from no-direct-write-to-responsewriter.}

[semgrep-app]

Semgrep found a possible database connection string built with string concatenation. Check for proper encoding/escaping of components to prevent parse errors and injection vulnerabilities.

_{Ignore this finding from db-connection-string.}

[semgrep-app]

Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L345 - Triage

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.

_{Ignore this finding from no-direct-write-to-responsewriter.}