Move optimade dependency as extra dependency

[unkcpz]

No description provided.

[unkcpz]

Here is the attempt of moving optimade as an extra effort #554. I think we want it anyway.

The test failed expect because the aiida-core is update to 2.5.0. I am a bit confused on what we really try to compatible with all these versions pinned?

[unkcpz]

A real case in my mind is if the user have a workable AiiDAlab environment with aiida-core==2.4.0, if they upgrade the aiidalab-widgets-base with the pinning of aiida-core>2.1,<3, the aiida-core will not be updated to aiida-core==2.5.

[unkcpz]

after #556

[codecov]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (21dfc5d) 87.16% compared to head (4a85ac1) 87.07%.

Files	Patch %	Lines
aiidalab_widgets_base/databases.py	40.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #554      +/-   ##
==========================================
- Coverage   87.16%   87.07%   -0.09%     
==========================================
  Files          27       27              
  Lines        4642     4650       +8     
==========================================
+ Hits         4046     4049       +3     
- Misses        596      601       +5     

Flag	Coverage Δ
python-3.10	87.07% <40.00%> (?)
python-3.8	87.10% <40.00%> (?)
python-3.9	87.10% <40.00%> (-0.06%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[danielhollas]

Looking at the OptimadeQueryWidget, it seems pretty self-contained and not dependent on other AWB widgets. Therefore, I think it would make sense to push it out of AWB to the new ipyoptimade package.
There might be downsides but imo it's worth exploring.

It would also make it easier for AiiDAlabs Apps to migrate to this package, since it would be more independent of the AWB version (e.g. one could switch to the new ipyoptimade widget even with AWB 2.1.0. (unless there are some optimade dependency clashes).

CC @yakutovicha might have more context here, as he was involved in a decision to move the widget here per #130

[danielhollas]

There's actually a long discussion about whether to include this OPTIMADE widget in AWB on this PR:

#131

I think we need to read through the arguments there and decide if they are still valid (especially given that we want to integrate AWB in the Docker image).

[danielhollas]

I think this moves us in the right direction so I think this is good to merge now and iterate on it.

@unkcpz just one request, could you please provide a screenshot of what happens when you try to load QeApp with this version but the optimade_client package is not available?

[unkcpz]

This is how it looks like. I made a change in the last commit to use <code>optimade-client</code> to format it.

[danielhollas]

Thanks. I wonder if more formatting would be warranted (e.g. maybe using the bootstrap error class or something like that to get a reddish box around it. Currently it's not immediately clear that it's an error.

Leaving that up to you.

[unkcpz]

I agree, it is not so clear. I change it to

[danielhollas]

Perfect, thanks!

[unkcpz]

I quite like the appearance. I feel comfortable when the whole line filled, so I merge it ^^