Release explorer as npm package

[MatiasOS]

Description

Add npm publishing capability to release the pre-built explorer as an npm package (@openscan/explorer). This enables downstream projects to consume the built explorer assets directly from npm.

Related Issue

Closes #118

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactoring
• Performance improvement
• Other (please describe):

Changes Made

• Add GitHub Actions workflow (publish-npm.yml) that automatically publishes to npm on merge to main
• Create dist-package.template.json with npm package metadata for @openscan/explorer
• Update build-development.sh to generate dist/package.json with version from main package.json
• Add publish:dist npm script for manual publishing

Screenshots (if applicable)

N/A

Checklist

• I have run npm run format:fix and npm run lint:fix
• I have run npm run typecheck with no errors
• I have run tests with npm run test:run
• I have tested my changes locally
• I have updated documentation if needed
• My code follows the project's architecture patterns

Additional Notes

The workflow uses JS-DevTools/npm-publish@v4 with provenance enabled for supply chain security. The package is published with public access to the @openscan scope.

[github-actions]

🚀 Preview: https://pr-178--openscan.netlify.app
📝 Commit: 71e5ebfabcaf122cb7ad713570742014ba80112f