Nested activation of Mocket doesn't cleanly restore patches

[ento]

Noticed this while trying to upgrade mocket. The project I'm working with has tests that have the @mocketize decorator and also depend on a pytest fixture that enables Mocket in strict mode. Subsequent tests that make actual HTTP requests fail due to Mocket's strict mode being still active, even though the tests don't use Mocket.

Minimal test case

def test_mocketize_twice_nested():
    with Mocketizer(strict_mode=True):
        with Mocketizer(strict_mode=True):
            pass

    url = "http://httpbin.local/ip"
    assert httpx.get(url).status_code == 200

Failing CI run: https://github.com/ento/python-mocket/actions/runs/32912004754/job/98007893977?pr=1

>       raise StrictMocketException(msg)
E       mocket.exceptions.StrictMocketException: Mocket tried to use the real `socket` module while STRICT mode was active.
E       Attempted address: httpbin.local:80
E       Sent data: GET /ip HTTP/1.1
E       Registered entries:

Mocket version: 3.14.3, seems to have regressed since 3.13.3

Prior to 3.13.3, references to true socket objects were kept as module-level variables in mocket.py, while the new approach in inject.py overwrites original values when Mocket gets enabled when it's already active.

[mindflayer]

I've just released a new version fixing the regression, I'm sorry the use-case was not covered by proper tests:
https://pypi.org/project/mocket/3.14.4/

[ento]

Thank you for the quick fix!