feat: add HOL Guard tool

[kantorcodes]

Summary

Adds HOL Guard as a standalone Trunk tool backed by the stable hol-guard PyPI package.

• exposes the hol-guard shim through Trunk's default plugin source
• pins current stable known_good_version to 2.2.126
• adds a hol-guard --version semver health check
• adds the repository-native toolInstallTest

This follows the current tools/ contribution pattern for Python runtime packages. PyPI currently identifies 2.2.126 as the stable release and documents hol-guard --version as the installed command verification path.

Validation

• fresh upstream issue, PR, and code searches found no existing HOL Guard entry before the original submission
• manifest/test structure mirrors existing Trunk Python tools and hyphenated tool naming
• refreshed both the manifest pin and install-test version to the current stable PyPI release

I could not run the full local trunk check in the connected execution environment, so I am not claiming that as passed; the repository-native install test is included for CI.

Affiliation: I maintain HOL Guard / Hashgraph Online. AI assistance was used to prepare this focused contribution and the version refresh.

[trunk-io]

✨ Submitted to Merge by @kantorcodes. It will be added to the merge queue once all branch protection rules pass and there are no merge conflicts with the target branch. See more details here.

[kantorcodes]

/trunk merge

[kantorcodes]

/trunk merge

[trunk-io]

An error occurred while submitting your PR to the queue: Only users that are a part of this repo's Trunk organization or have write permissions to the repo can submit a PR to the queue

[kantorcodes]

All required changes are in and the PR is still mergeable. The queue command now reports that only a repo member or someone with write access can submit it. Could a maintainer add #1163 to the merge queue when convenient? I’ll handle any requested changes right away.