⚠️ Warning: update public SECURITY.md reporting instructions

[jeff-at-trimble]

⚠️ Warning: this is a proactive compliance update ahead of trimble-oss/oss-overseer#170.

Why this PR exists

A public policy update is queued in oss-overseer that will require public repositories to do both of the following in SECURITY.md:

1. Include the Trimble public security form URL:

   https://www.trimble.com/en/our-commitment/responsible-business/data-privacy-and-security/report-cybersecurity-issues/form
   

2. Stop using cybersecurity@trimble.com, which is for internal use only.

What this PR changes

• updates the Reporting a Vulnerability section to point to the approved public form
• removes the internal-only email address
• leaves the rest of the file unchanged

Why this matters

If trimble-oss/oss-overseer#170 merges before this repo updates SECURITY.md, the next public audit will report a new MUST violation for this repository.

This PR is meant as an early warning and a low-noise fix before that rollout happens.

[github-actions]

Super-linter summary

Language	Validation result
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
MARKDOWN	Pass ✅
MARKDOWN_PRETTIER	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter