chore: harden repository security

[cmilesio]

What

Add a repeatable security pipeline across Console and its three Go modules.

Boundary	Enforced behavior
Workflow code	Actions pinned to immutable commits with least-privilege permissions
Empty and command modules	Package discovery distinguishes truly empty modules and test-compiles the rest
Local examples	./.. preserves sibling resolution and produces canonical SBOM identity
SBOM content	JSON, library type, test dependencies, nonempty contents, and exact count
Dependency graph	Root and examples select golang.org/x/sys 0.44

The fixed x/sys release requires Go 1.25, so the root and examples modules move from Go 1.24 to Go 1.25. No public API, configuration, persisted-data, or runtime behavior changes. Console publishes source modules, so there is no release binary to attest.

Why

The PR makes security coverage follow the module graph automatically. That keeps a future docs, examples, or integration module from silently falling outside scanning and dependency maintenance, while removing the current system-call dependency advisory.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.