feat: prepare hSQLite Editor for open-source release

[helbertm]

Summary

• modernize the standalone SQLite editor architecture, editor runtime, UX, accessibility, and en-US/pt-BR/es-ES localization
• deliver the backlog features, deterministic Linux staging, SBOM/runtime provenance, privacy documentation, and reproducible validation gates
• add repo-owned GitHub control auditing and draft-first immutable release publication with exact assets and attestations
• harden release input validation, inline-script inspection, workflows, permissions, dependency review, CodeQL, browser quality, and Linux validation

Validation

• npm run test:unit (32/32)
• npm run validate:full:ci
• npm run validate:release-assets
• npm run quality:docker
• npm run quality:security:docker (0 npm and OSV findings)
• locale/accessibility browser matrix and native standalone browser checks
• deterministic Linux staging and scoped secret scans

Hosted governance

• active master-protection ruleset with pull requests, linear history, conversation resolution, squash/rebase only, deletion and force-push protection
• seven exact required checks: Quality Gate, Linux Package, Browser Quality, CodeQL Analysis, aggregate CodeQL, Commit Convention, and Dependency Review
• immutable releases, Private Vulnerability Reporting, dependency graph, Dependabot security controls, restricted action sources, full-SHA action enforcement, external-contributor approval, read-only default token, and Pages administrator-bypass protection enabled
• Release Please pull-request authority retained with explicit job-level permissions

Release boundary

This pull request hardens master. Publication remains draft-first and must produce exactly hsqlite-editor-v0.3.143, hSQLite-Editor-v0.3.143.html, sbom.spdx.json, SHA256SUMS, and both digest-bound attestations. No incomplete public release is allowed.

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