[csolution] Incompatible major versions in .csloution and .clayer do not cause failure

[MiloradCvjetkovic]

Bug description
When a required pack version is specified in the .csolution.yml file with a higher major version then in some of the clayer.yml files, the csolution accepts pack with version as specified in the .csolution.yml file but it does not complain or fail due to incompatible version being required by the .clayer.yml file.

To Reproduce
Specify different major versions for a pack requirement in .csolution.yml and .clayer.yml files.

Expected behavior
csolution should report incompatible version required by .csolution.yml and .clayer.yml and fail.

Environment

• Arm CMSIS Solution v1.66.0
• OS: Win11

[jkrech]

There is currently no rule that requires multiple selected pack versions to have the same major version number.
The rule exists that if component versions are not explicitly specified, the highest version gets selected from which ever pack version it originates from (most likely from the highest pack version). Using component versions it is possible to select components from different pack versions regardless how different they are.

csolution should probably warn about multiple effective pack versions being selected, even though in rare cases this may be intentional.

[brondani]

Loading multiple pack versions has been discussed several times in the past, it was always allowed and we have even implemented improvements such as the correct API resolution and the re-use of packs when the specified version ranges intersect, for example:
#1124
#2191
Also note that the parent file where packs are required [csolution|cproject|clayer].yml does not play any role, all entries have the same weight.