SONARPY-2355 Update licenses to SSALv1

[guillaume-dequenne-sonarsource]

Context for the format update of license-maven-plugin: see this PR. Not respecting the new format prevented our custom configuration from being taken into account (Python files were neither checked nor updated).

Currently, SSALv1 itself is flagged as a forbidden dependency for our internal checks. Because of this, they are overridden in our checks (see BUILD-7017).

[Seppli11]

Apart from the missing link to the license file, it looks good to me.

SQRP-80 mentions that projects that should remain under LGPL need to modify the pom.xml accordingly. But this doesn't apply to any of the projects in this repo, right?

[Seppli11]

According to SQRP-80, the readme should link to the LICENSE.txt file

[guillaume-dequenne-sonarsource]

Apart from the missing link to the license file, it looks good to me.

SQRP-80 mentions that projects that should remain under LGPL need to modify the pom.xml accordingly. But this doesn't apply to any of the projects in this repo, right?

It would apply to the sonar-scanner-python, if it were a maven project, but it's not so it should be okay (we should prevent the license from being updated automatically though - I don't remember how this is handled for Python project)

That said, the serializer under this repo should also move to SSALv1, and I realize my initial changes didn't account for that.

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[Seppli11]

LGTM