Random Error with python3 v3.14

Nessuno ha ancora preso questa issue.

### How to replicate
On lightning v26.04rc2, running any test suite with MacOS M5 Tahoe 26.4, having python v3.14 installed, this error completely random appear:

```
Traceback (most recent call last):
  File "/Users/X/Documents/v26.04rc2/.venv/bin/pytest", line 10, in
    sys.exit(console_main())
             ~~~~~~~~~~~~^^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/_pytest/config/__init__.py", line 223, in console_main
    code = main()
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/_pytest/config/__init__.py", line 193, in main
    config = _prepareconfig(new_args, plugins)
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/_pytest/config/__init__.py", line 361, in _prepareconfig
    config: Config = pluginmanager.hook.pytest_cmdline_parse(
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        pluginmanager=pluginmanager, args=args
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/pluggy/_hooks.py", line 512, in __call__
    return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)
           ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/pluggy/_manager.py", line 120, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
           ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/pluggy/_callers.py", line 167, in _multicall
    raise exception
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/pluggy/_callers.py", line 139, in _multicall
    teardown.throw(exception)
    ~~~~~~~~~~~~~~^^^^^^^^^^^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/_pytest/helpconfig.py", line 124, in pytest_cmdline_parse
    config = yield
             ^^^^^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/pluggy/_callers.py", line 121, in _multicall
    res = hook_impl.function(*args)
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/_pytest/config/__init__.py", line 1186, in pytest_cmdline_parse
    self.parse(args)
    ~~~~~~~~~~^^^^^^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/_pytest/config/__init__.py", line 1539, in parse
    self.pluginmanager.load_setuptools_entrypoints("pytest11")
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/Users/X/Documents/v26.04rc2/.venv/lib/python3.14/site-packages/pluggy/_manager.py", line 416, in load_setuptools_entrypoints
    plugin = ep.load()
  File "/opt/homebrew/Cellar/python@3.14/3.14.3_1/Frameworks/Python.framework/Versions/3.14/lib/python3.14/importlib/metadata/__init__.py", line 179, in load
    module = import_module(match.group('module'))
  File "/opt/homebrew/Cellar/python@3.14/3.14.3_1/Frameworks/Python.framework/Versions/3.14/lib/python3.14/importlib/__init__.py", line 88, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "", line 1398, in _gcd_import
  File "", line 1371, in _find_and_load
  File "", line 1314, in _find_and_load_unlocked
  File "", line 491, in _call_with_frames_removed
  File "", line 1398, in _gcd_import
  File "", line 1371, in _find_and_load
  File "", line 1335, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'pytest_trackflaky'
```

You have to run `uv run make clean` and reinstall everything to continue testing.

Riproduci il problema eseguendo una suite di test con Python 3.14 su macOS M5 Tahoe e ispeziona l’entry point .venv/bin/pytest e il traceback del caricamento dei plugin di pytest. Controlla il modulo mancante pytest_trackflaky, quindi confronta il comportamento prima e dopo `uv run make clean` e la reinstallazione delle dipendenze. Il lavoro è completato quando le esecuzioni ripetute della suite di test non incontrano più questo errore di importazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.