Set installability analysis workflow (WIP)

[jaimergp]

We are testing for:

• Creating an environment with Python, latest napari for pyside and all plugins at once
• Same, but one environment per plugin. They all should be individually installable in at least one platform.
• The matrix covers four platforms (Linux and Windows x64, plus macOS Intel/M1), and Python 3.8, 3.9 and 3.10.
• The exit codes for each task reflect the number of problems. These can be seen from the Summary page of each run, and do not expire :D Useful to track how rough the landscape is over time.

The time spent in each combination is super interesting, which gives you an idea on how different the packaging landscapes are across platforms!

[jaimergp]

@goanpeca Can you take another look? I think I covered your suggestions.

This is just the beginning of what we can test against, and it already gives some interesting insights. For example, a few packages brought in pyqt or derivatives even when nobody asked for it. Following that thread, we can see that this package requires pyqt! I think it'll be an interesting exercise to minimize the number of conflicts.

[goanpeca]

This is just the beginning of what we can test against, and it already gives some interesting insights. For example, a few packages brought in pyqt or derivatives even when nobody asked for it. Following that thread, we can see that this package requires pyqt! I think it'll be an interesting exercise to minimize the number of conflicts.

This is pretty cool and will help a lot :) !