Think about ways to "share" configuration

[sschuberth]

When browsing a result with the workbench, the local configuration (like package configurations) is applied. This might not be what the user expects when trying to reproduce results from an ORT run in CI which might use a different configuration.

Some rough orthogonal ideas how to address that:

• Make in easy in the work bench to use another (remote) configuration (repository).
• Really "bake" all configuration into the regular ORT result.
• Allow the workbench to only load a "special" report format similar to the current evaluated model report format (but created in a much more sane way, which Jackson indices etc.) which contains all required information. Such a report format could also use a dedicated file extension that could be associated to the workbench, so that double-clicking on such a file opens it up directly in the workbench.

[mnonnenmacher]

My prefered solution to this would be to wait until oss-review-toolkit/ort#6188 (comment) is implemented and then add an option to the workbench to use only the configuration (curations, package configurations, ...) contained in the loaded OrtResult file.