fix: add repository metadata so the npm provenance publish succeeds

[souf92i]

Summary

Fixes the failed Release run after v1.0.0. The release publishes to npm with provenance (publishConfig.provenance: true + NPM_CONFIG_PROVENANCE: 'true' in release.yml), and npm rejects a provenance publish unless package.json has a repository.url matching the GitHub repo. The field was missing, so the first publish failed:

npm error 422 ... Error verifying sigstore provenance bundle:
package.json: "repository.url" is "", expected to match "https://github.com/evertrust/stream-mcp"

This adds repository (plus bugs / homepage). No code changes.

Recovery note

v1.0.0 cut a git tag but nothing was published to npm and no GitHub release was created. Merging this is a fix:, so the next release publishes v1.0.1 as the first real npm version; the unused v1.0.0 tag is left as-is (chosen over deleting a remote tag).

Test plan

• package.json valid; repository.url resolves to https://github.com/evertrust/stream-mcp
• prettier clean; commitlint-compliant fix: message
• After merge: confirm the Release workflow publishes v1.0.1 with a valid provenance attestation