ci: add security, coverage, and release automation

[BigDella]

Summary

• make high-severity dependency audits fail and publish production license reports
• add CodeQL analysis for TypeScript and a dedicated coverage job using the existing Vitest thresholds
• automate semantic-versioned changelog, GitHub release, and npm publishing with Release Please
• refresh contributor setup, validation, issue links, and release documentation

Verification

• git diff --check passes
• Local dependency installation was attempted but did not complete in this environment; CI will run typecheck, lint, tests, coverage, and build.

Closes #800
Closes #801
Closes #802
Closes #799

[drips-wave]

@BigDella Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[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.