Baseline package validator should allow breaking changes in major versions

[Piedone]

Is your feature request related to a problem? Please describe.

Baseline package validator will fail the validation between any two versions if there are breaking changes. This happens also between two major versions (e.g. when going from 1.2.3 to 2.0.0). However, according to SemVer 2.0.0, breaking changes are allowed in major versions.

Describe the solution you'd like

The validator IMO shouldn't raise validation errors when going to a greater major version (at least in a configurable way). Alternatively, it may raise a warning only.

Additional context

I noticed this when going from v9.1.1 to v10.0.0 with our Lombiq UI Testing Toolbox for Orchard Core project. I have some memory that the behavior I'm describing was actually the case before, but currently (.NET 8.0.300) it certainly isn't.

[dotnet-policy-service]

@dotnet/area-infrastructure-libraries a new issue has been filed in the ApiCompat area, please triage