Fix Windows startup and portable memory reporting

[Bortlesboat]

Fixes #33.

Importing the queue on Windows currently fails because Python's resource module is unavailable. Use psutil to report the current process's RSS in MiB and add a Windows CI smoke test that imports the queue and exercises memory reporting.

The dependency range also keeps FastMCP on its supported 2.x API. A fresh install otherwise selects FastMCP 4, which no longer provides the fastmcp.tools.tool import used by this project.

The memory helper now reports current RSS, as its docstring describes, instead of the lifetime peak returned by ru_maxrss. Memory deltas can therefore become negative when memory is released. Task scheduling and cancellation are unchanged; this does not claim full Windows cancellation support.

Validation:

• Reproduced the original ModuleNotFoundError: resource with the new regression test.
• Native Windows, clean Python 3.12 environment: import/RSS regression passes; Ruff passes.
• Linux, Python 3.12: all 91 tests pass. The local WSL run used COLUMNS=512 so ps returned complete arguments for the existing process-identification tests.

Manually reviewed the four-file diff, including subprocess isolation, RSS conversion, and the retained Linux workflow.

[Bortlesboat]

detects commit SHAs that don't match their version comment tags

Corrected the version comments in 580a5f6: the existing checkout pin is v6.0.2, and the setup-uv pin is v7.3.0. Verified both against their repositories' release tags and updated both jobs consistently. The action SHAs and executable workflow content are unchanged.

[Bortlesboat]

Semgrep, zizmor and DCO passed, but CI 34256977533 ended without executing jobs after the approval wait. The Windows job is important here: importing resource breaks startup on that platform, and the patch uses current RSS from psutil instead of the platform-specific lifetime peak. The separate FastMCP constraint retains the project's supported 2.x import API.

Could a maintainer approve/rerun CI for 580a5f6 so the Windows smoke job and retained Linux suite execute? The action-version comments have already been corrected in that head; no empty commit has been added to trigger the gate.