Stop test_ssl from changing environment

On my Win10, buildt yesterday and today, py -m test and py -m test test_ssl sometimes (>50%) changes the environment, which is a failure for the whole suite (test alone).

0:01:43 load avg: 2.28 [466/485/1] test_ssl failed (env changed) (31.1 sec) -
Warning -- warnings.filters was modified by test_ssl
Warning --   Before: (2199023321584, [], [])
Warning --   After:  (2199661512208, [('always', None, <class 'ResourceWarning'>, None, 0)], [('always', None, <class 'ResourceWarning'>, None, 0)])

About 5 runs with -v added don't show this, though there are a few hundred lines of output with several ssl error tracebacks that do not cause a test failure.

Might just be my machine if no CI errors.

EDIT: py ran installed 3.14.0a5. Just reran twice with today's buld with python ... to run the build and got the same. Install is norma + gil. Build is debug no-gil.

Installed new 3.14.0a6 and ran 5 times without failure. I rechecked and my python build with the problem is post-release 3.14.0a6+.

Start by running py -m test test_ssl and the full py -m test suite on the reported Windows debug no-GIL build, comparing runs with and without -v. Investigate the reported warnings.filters environment change and ssl error tracebacks; done means repeated runs no longer report test_ssl failed (env changed).