Add button to trigger the update of the results tabs.

[superstar54]

In PR #844 , the process monitor updates the result tabs in another thread. This leads to an issue: when the user interacts with the result, the widget runs in the thread differently from the one running in the process monitor.

Therefore, triggering the automatic updating of the result tabs is not possible.

In this PR, we don't use process monitor anymore. Instead, we add a button to let the user trigger the update manually.

I also modified the layout of the buttons (kill, clean) to make the UI pretty.

[codecov]

Codecov Report

Attention: Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.

Project coverage is 67.09%. Comparing base (c4a453b) to head (69b397b).
Report is 121 commits behind head on main.

Files with missing lines	Patch %	Lines
src/aiidalab_qe/app/result/__init__.py	60.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #868      +/-   ##
==========================================
- Coverage   67.10%   67.09%   -0.02%     
==========================================
  Files          51       51              
  Lines        4688     4692       +4     
==========================================
+ Hits         3146     3148       +2     
- Misses       1542     1544       +2     

Flag	Coverage Δ
python-3.11	67.09% <71.42%> (-0.02%)	⬇️
python-3.9	67.12% <71.42%> (-0.02%)	⬇️

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.

[mikibonacci]

Hi @superstar54 , thanks for this and for improving the other buttons.

Just thinking if we can somehow avoid to render again the tabs if they are already there, but I also think that this will be not a problem when the lazy loading will be there.

So, LGTM!

[superstar54]

Just thinking if we can somehow avoid to render again the tabs if they are already there, but I also think that this will be not a problem when the lazy loading will be there.

Indeed, this is the problem from the node tree. There is a PR to fix it: #560. Will reopen it soon.