ci: add security scanning workflows and release tooling

[yogeshchoudhary147]

Mirrors the CI and release setup from auth0-spa-js.

Security scanning

• CodeQL: Static analysis on PRs, pushes to main, and weekly schedule
• Snyk: Dependency vulnerability checks on PRs, pushes to main, and bi-monthly schedule
• SCA: Software Composition Analysis via auth0/devsecops-tooling reusable workflow on PRs and pushes to main
• RL Secure: ReversingLabs binary scanner wired into the release workflow as a gate before npm publish

Release tooling

• .shiprc: Configures @a0/ship to bump .version and regenerate docs on release

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