Make the primary package ID syntax configurable

[sschuberth]

Esp. when interacting with other compliance tools, e.g. in the context of the OCCTET project, it can be confusing for users that ORT Server is the only tool that uses ORT's package IDs to refer to packages. Instead, using package URLs (purl) probably is a better choice, esp. with purl emerging as an ECMA standard.

However, as right now quite a bit of project-specific configuration still needs to be done in one of ORT's configuration files as no UI to do the same exists, and these configuration files often need to refer to packages via ORT's IDs, also the latter should still be available for easy copying & pasting.

So the idea is to make the primary package ID that ORT Server uses throughout the UI should become configurable per user. That way, users can switch depending on their background (existing ORT users or new ORT Server users), and no screen space is "wasted" by displaying both ORT's IDs and purls in all places.

[Etsija]

Concerning tables showing either package ID or purl, @lamppu and I played around with an idea to simply define both columns, but just make one of them visible/rendered in the UI, as that would be quite easy to do by changing the column's visibility property (based on the user's preference to show either package IDs or purls). I don't think that would cause much overhead/delay concerning the UI, as both IDs are anyway included in the data fetched from the back-end endpoints I believe.

[sschuberth]

I guess whether that approach works might depend on the column header to use, or? Like, say the column should be named "Package ID" independently of the configured primary package identifier, would that be possible?