[pull] master from daquinoaldo:master - #13

# Pull Request Details

## Related Issue
Addresses #77.

Importing `https-localhost` currently installs a process-wide
`uncaughtException` handler even when the package is only used as a
module. That changes application-level error handling and can hide the
original stack-trace behavior.

This change scopes the existing handler to the CLI path (`require.main
=== module`) so the CLI keeps its friendly `EACCES` / `EADDRINUSE`
messages while library consumers no longer get a global process listener
as a side effect of `require("https-localhost")`.

A regression test re-imports the module after clearing the require cache
and verifies that the `uncaughtException` listener count does not
change.

## Types of changes
- [ ] Docs change / refactoring / dependency upgrade
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)

## Checklist
- [x] My code follows the code style of this project.
- [x] I have updated the documentation or my changes dont require it.
- [x] I have read the CONTRIBUTING document.
- [x] I have added tests to cover my changes.
- [ ] All new and existing tests passed.

Configure the release workflow for npm Trusted Publishing via GitHub
OIDC. Supports publishing the already-tagged v4.7.2 without creating
another version bump.

Bump release runner to Node 24 for npm Trusted Publishing OIDC support,
and consolidate the release action into a single `upgrade` input with
options: `patch`, `minor`, `major`, and `existing` (publish without
re-bumping).