enso/tools/legal-review/AWS/report-state

A2A8F62C19783E738C3CE19C8206799E0CA4B6D539DBEDCDCB0ED73713DE47FF
2C988BD54A93DBEFA6A01D231C63CBA7C2A2430DA09508C1EDE589BDFFACF00E
0
Add AWS SSO JARs to the `Standard.AWS` library (#9782) As reported by our users, when using the AWS SSO, our code was failing with: ``` Execution finished with an error: To use Sso related properties in the 'xyz' profile, the 'sso' service module must be on the class path. ``` This PR adds the missing JARs to fix that. Additionally it improves the license review tool UX a bit (parts of #9122): - sorting the report by amount of problems, so that dependencies with unresolved problems appear at the top, - semi-automatic helper button to rename package configurations after a version bump, - button to remove stale entries from config (files or copyrights that disappeared after update), - button to add custom copyright notice text straight from the report UI, - button to set a file as the license for the project (creating the `custom-license` file automatically) - ability to filter processed projects - e.g. `openLegalReviewReport AWS` will only run on the AWS subproject - saving time processing unchanged dependencies, - updated the license search heuristic, fixing a problem with duplicates: - if we had dependencies `netty-http` and `netty-http2`, because of a prefix-check logic, the notices for `netty-http` would also appear again for `netty-http2`, which is not valid. I have improved the heuristic to avoid these false positives and removed them from the current report. - WIP: button to mark a license type as reviewed (not finished in this PR). 2024-04-25 21:44:51 +03:00			`A2A8F62C19783E738C3CE19C8206799E0CA4B6D539DBEDCDCB0ED73713DE47FF`
			`2C988BD54A93DBEFA6A01D231C63CBA7C2A2430DA09508C1EDE589BDFFACF00E`
Separating Redshift connector from `Database` library into a new `AWS` library (#6550) Related to #5777 2023-05-04 20:36:51 +03:00			`0`