Google colab gives weird error when gemmi/spglib are imported

[tkittel]

As discussed with @marquezj @dddijulio:

In a google colab environment where ncrystal, gemmi, and spglib are all pip installed, using the NCrystal cifutils results in warnings when gemmi or spglib are imported by NCrystal:

Querying the Crystallography Open Database for entry 9008590
<frozen importlib._bootstrap>:914: ImportWarning: _PyDrive2ImportHook.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _PyDriveImportHook.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _GenerativeAIImportHook.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _OpenCVImportHook.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: APICoreClientInfoImportHook.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _BokehImportHook.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _AltairImportHook.find_spec() not found; falling back to find_module()
Adding cod_9008590.cif to local file cache in $NCRYSTAL_ONLINEDB_CACHEDIR
Attempting to load CIF data with gemmi
Self-consistency of structure was verified by spglib
<frozen importlib._bootstrap>:914: ImportWarning: _PyDrive2ImportHook.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _PyDriveImportHook.find_spec() not found; falling back to find_module()
...

If we explictly import gemmi + spglib earlier in the notebook, these warnings disappear.

The question is whether or not we are doing something wrong, or if there is an easy and maintainable way to get rid of them by modifying the NCrystal importing code (we could of course suppress them)