chore: use https repository metadata

[aldorac337]

Summary

• Update package repository metadata from git:// to git+https.
• Leave runtime code, dependencies, package version, homepage, bugs, license, and package files unchanged.

Validation

• node -e "const p=require('./package.json'); if (p.name !== 'error-stack-parser') throw new Error('name mismatch'); if (p.repository?.url !== 'git+https://github.com/stacktracejs/error-stack-parser.git') throw new Error(JSON.stringify(p.repository)); console.log(JSON.stringify(p.repository))" passed.
• git diff --check passed.
• npm ci --ignore-scripts --no-audit --no-fund completed with existing dependency deprecation warnings only.
• npm pack --dry-run --json passed after dependency install.
• ./node_modules/.bin/eslint . passed.
• Karma/Jasmine specs passed in local Chrome no-sandbox run: 25 of 25 successful.

Note: this repository's default npm test path still targets PhantomJS. On this local modern Node environment, karma-phantomjs-launcher fails during plugin loading before running tests, so I validated the same Karma/Jasmine spec files with Chrome instead.