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 the validated known_good_version to 3.0.18
• adds a hol-guard --version semver health check
• adds the repository-native toolInstallTest

This follows the current tools/ contribution pattern for Python runtime packages. HOL Guard v3.0.18 is the validated stable release used by this contribution and documents the installed hol-guard CLI as the runtime entrypoint.

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 3.0.18
• HOL Guard's Publish to PyPI workflow completed successfully for the v3.0.18 release commit

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 release refresh.

[trunk-io]

❌ This pull request was removed from the merge queue because it failed tests. PR #1173 was used for testing. See more details here.

Failed Required Status	Conclusion
Aggregate Test Results	Failure

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted 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.

[EliSchleifer]

LGTM. Thanks