Add canery to the tools list in README

[rluders]

Added canery project to the list of tools in README.

Required links

• Forge link (github.com, gitlab.com, etc): https://github.com/rluders/canery
• pkg.go.dev: https://pkg.go.dev/github.com/rluders/canery
• goreportcard.com: https://goreportcard.com/report/github.com/rluders/canery
• Coverage service link (codecov, coveralls, etc.): https://codecov.io/gh/rluders/canery

Pre-submission checklist

• I have read the Contribution Guidelines
• I have read the Quality Standards

Repository requirements

• The repo has a go.mod file and at least one SemVer release (vX.Y.Z).
• The repo has an open source license.
• The repo documentation has a pkg.go.dev link.
• The repo documentation has a goreportcard link (grade A- or better).
• The repo documentation has a coverage service link.

Pull Request content

• This PR adds/removes/changes only one package.
• The package has been added in alphabetical order.
• The link text is the exact project name.
• The description is clear, concise, non-promotional, and ends with a period.
• The link in README.md matches the forge link above.

Category quality

• The packages around my addition still meet the Quality Standards.

[github-actions]

Automated Quality Checks

Required checks

✅ Repo: accessible, has go.mod and SemVer release
✅ pkg.go.dev: OK
✅ Go Report Card: OK (grade unknown)

Additional checks

✅ License: MIT
⚠️ Maturity: repo appears to have less than 5 months of history

How to fix: Your repository needs at least 5 months of history since the first commit.
Please resubmit after the repository meets this requirement.
✅ CI/CD: GitHub Actions workflows detected
✅ README: present
⚠️ Coverage: missing from PR body
How to fix: Add a coverage service link to your PR description:

Coverage: https://app.codecov.io/gh/your-org/your-project

Popular options: [Codecov](https://codecov.io), [Coveralls](https://coveralls.io). Integrate one with your CI to track coverage automatically.


_These checks are automated and do not replace maintainer review. See [CONTRIBUTING.md](https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md) for full guidelines._

---

## PR Diff Validation

### Content checks

✅ **Files changed**: only README.md
✅ **Single item**: one package added
✅ **Link consistency**: README link matches forge link in PR body
✅ **Link text**: matches repository name
✅ **Description**: ends with punctuation
✅ **Description tone**: no promotional language detected
✅ **Category size**: Security has 52 items


_Automated diff validation — does not replace maintainer review._
<!-- Sticky Pull Request Commentpr-quality-check -->