Migrate to qtrio

[vxgmichel]

A draft for a potential qtrio migration.

This means we don't have to deal with separate qt/trio threads and that we can perform qt calls withing trio coroutines.

[codecov]

Codecov Report

Merging #1771 (c3302fc) into master (54133d2) will increase coverage by 0.00%.
The diff coverage is 83.90%.

@@           Coverage Diff            @@
##           master    #1771    +/-   ##
========================================
  Coverage   87.70%   87.70%            
========================================
  Files         245      245            
  Lines       23895    23795   -100     
========================================
- Hits        20957    20870    -87     
+ Misses       2938     2925    -13     

Impacted Files	Coverage Δ
parsec/core/gui/custom_dialogs.py	69.54% <0.00%> (-0.29%)	⬇️
parsec/core/gui/claim_device_widget.py	88.15% <33.33%> (-0.19%)	⬇️
parsec/core/gui/claim_user_widget.py	87.62% <45.45%> (-0.18%)	⬇️
parsec/core/gui/timestamped_workspace_widget.py	28.23% <50.00%> (-0.69%)	⬇️
parsec/core/gui/app.py	74.16% <59.37%> (-0.84%)	⬇️
parsec/core/gui/new_version.py	51.76% <62.50%> (-0.62%)	⬇️
parsec/core/gui/file_history_widget.py	79.59% <83.33%> (ø)
parsec/core/gui/files_widget.py	78.70% <87.93%> (+0.24%)	⬆️
parsec/core/gui/create_org_widget.py	87.39% <88.88%> (+0.05%)	⬆️
parsec/core/gui/trio_jobs.py	89.39% <89.39%> (ø)
... and 35 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 54133d2...c3302fc. Read the comment docs.

[vxgmichel]

A bit of cleanup is still needed, in particular:

• removing aqtbot.run
• removing job.cancel_and_join

[vxgmichel]

@touilleMan @Max-7 The PR is now ready to be reviewed :)

[touilleMan]

In theory this whole job system is no longer needed right ? (it is just kept to avoid a huge refactoring of the codebase)

[vxgmichel]

We still need a nursery with some throttle logic (submit_throttled_job), so it's still useful. Wrapping trio tasks as jobs that we can retrieve or cancel also makes sense. The major cleanup would be getting rid of the qt_on_success and qt_on_error signals.

[vxgmichel]

More clean up can still be done:

• Get rid of the _trio callback to _qt callback logic
• Get rid of the _success and _error signals

[vxgmichel]

122 signals and corresponding callbacks to migrate..

± git grep "pyqtSignal(QtToTrioJob)" | wc -l
122

[touilleMan]

lgtm