Make the package / project scanners configurable when creating a run

[sschuberth]

For other jobs / worker types, like advisors, we can already select in the UI which plugins to use. Not so for scanners yet.

Scanners are a bit special because we can select for projects and packages individually which scanner(s) to use for the respective entity. So the UI should not only have one group of check boxes to enable / disable scanner from, but two: One for project scanners, and one for package scanners. Both should offer the full list of scanner plugins.

[Etsija]

After team discussion, I believe I understand what's required. The problem is, the endpoint to request for a full list of plugins is admin only: https://eclipse-apoapsis.github.io/ort-server/api/get-installed-plugins which means only admins can form the list when creating an ORT run. I don't know if this is intentional or not, but it suggests that "ordinary" users cannot choose scanner plugins used per run. I think it should be clarified that this is OK.

[Etsija]

We discussed this more with our team today and saw many more things needing discussion, before this feature can be implemented, for example:

• DoubleOpen uses DOS Scanner for everything, but it is configured in the server script on our configuration repository, of which the UI has no information whatsoever
• I am sure other teams use a similar configuration concept for the scanner(s) they are using
• the question then is: what specifically would this feature do? Only possibly take more scanners into use than the ones already configured in the server deployment? And if so, I am sure the users would need to know about the "default scanner(s)" already in use (they cannot atm)