Fix multiprocessing logging with non-fork start methods

[CyberAuth]

Summary

Fixes a Python 3.14 multiprocessing compatibility issue that could prevent MANSPIDER console logging from functioning and could raise a weakref pickling error.

Root cause

The logging queue was created during module import. Under spawn and forkserver, child processes re-imported the module and created private queues without active listeners, so file logging continued while console records were lost.

MANSPIDER also passed its complete controller to spiderling processes. With multiple concurrent targets, the controller process pool contained an already-started Process. Its process finalizer contains a weak reference and cannot be serialized.

Parser subprocesses similarly received a bound Spiderling method, which pulled unnecessary live runtime state into the serialized object graph.

Fix

• Create the logging queue explicitly from the active multiprocessing context.
• Pass the queue to workers and configure logging within each process.
• Exclude parent-only process and SMB cache state from controller serialization.
• Pass parser workers only the picklable values required for their task.
• Close the listener and queue in a defined shutdown order.
• Preserve the process-based concurrency model without forcing fork.

Testing

• Python 3.13
• Python 3.14
• Existing pytest suite
• Regression coverage under fork, forkserver, and spawn
• Multi-target process communication
• Child-process console and file logging
• Ruff lint and formatting checks

Related work

This is a serialization-safe alternative to #96 and #106. It preserves the default multiprocessing context and the existing process-based worker architecture.

Security / data note

The reproduction and regression tests use synthetic data only and do not require access to external SMB infrastructure.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[CyberAuth]

I have read the CLA Document and I hereby sign the CLA

[CyberAuth]

recheck

[singlerider]

Solid fix with a clear explanation of the root cause. The serialization-safe approach and test coverage across all three start methods are exactly right. Minor nit: parse_file is now a no-op wrapper that could be inlined, and the bare except: blocks in manspider.py could be more specific. Otherwise, approved.