Make install-tool tool and tool version configurable

[swang392]

What this PR does / why we need it:

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

• fixes #

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• All commits are signed and show as "Verified" on GitHub (see: signing commits)
• Chart Version semver bump label has been added (use <chartName>/minor-version, <chartName>/patch-version, or <chartName>/no-version-bump)
• For datadog or datadog-operator chart or value changes, update the test baselines (run: make update-test-baselines)
• For datadog chart changes, received ✅ from a member of your team

GitHub CI takes care of the below, but are still required:

• Documentation has been updated with helm-docs (run: .github/helm-docs.sh)
• CHANGELOG.md has been updated
• Variables are documented in the README.md

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c1255faf29

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Quote installInfo values in rendered install_info YAML

The new datadog.installInfo.tool and toolVersion values are now user-controlled, but they are injected as unquoted scalars into the embedded install_info YAML. If either value contains YAML-significant content (for example ": ", #, or a newline), the resulting install_info payload can be parsed incorrectly or become invalid when the Agent reads it, which defeats the purpose of making these fields configurable. Rendering these fields with quoting (or JSON string escaping) avoids this regression while preserving arbitrary string input.

Useful? React with 👍 / 👎.