Compatible layer detection only considers connections from first project in multi-project solution

[MiloradCvjetkovic]

Bug description
When a template's solution contains multiple projects, compatible layer detection considers only connections (consumes) from first project.

To Reproduce

• install released Alif Ensemble pack
• build and install development version of the SDS-Framework pack from https://github.com/ARM-software/SDS-Framework
  • open ARM/SDS/2.0.1-dev<num>/template/algorithm/AlgorithmTest.cproject.yml file and change line:
    - Heap: 65536
    to
    - Heap: 131072
• open VS Code - Arm CMSIS Solution extension
• select Create Solution
• select Target Board DevKit-E7 (Gen 2)
• under Templates select SDS
• choose a folder
• click on Create button

you will be offered Add software layer with Board Layer, but Board layers located in AlifSemiconductor/Ensemble/2.0.4/Boards/DevKit-e7/Layers/M55_HE/Board_HE.clayer.yml and AlifSemiconductor/Ensemble/2.0.4/Boards/DevKit-e7/Layers/M55_HP/Board_HP.clayer.yml both contain setting Heap: 98304 which is insufficient to our edited Heap: 131072 required by the second project AlgorithmTest thus should not be available for selection as they do not satisfy conditions for both projects from the solution.

Environment:

• Arm CMSIS Solution v1.64.2
• OS: Win11

Enhancement suggestions
These situations are hard to debug because there is no additional information to why there was no compatible layer (not in this situation when it is available when it shouldn't be).
It should be possible for user to see if selected template does not have a compatible layer provided by the Target Board, and possibly which condition isn't satisfied.
Possibly it should not even be possible to select template with a board that does not even have a compatible layer.

[jkrech]

The root cause for the fact that only one project is considered could be that the specified target-set (as well as the default target-set) only specifies one project context. csolution list layers gets invoked with an active target-set and does not know about the other project. Therefore no intersection satisfying both project contexts gets created.

[brondani]

The target-set defined in the SDS-Framework has only one project-context: DataTest.DebugRec, so this is the only context considered by DiscoverLayers as long as this is the only possible active target-set being defined.

For development debug purposes, csolution list layers command with --debug flag can be used to print all checked layer combinations and invalid connections, e.g.:

$csolution list layers USB_Device.csolution.yml -a STM32U585AIIx --debug
debug csolution: check for context 'HID.Debug+STM32U585AIIx'

check combined connections:
  D:/examples/USB_Device1/HID/HID.cproject.yml
    (USB Device HID)
  D:/examples/USB_Device1/Board/B-U585I-IOT02A/Board.clayer.yml
    (B-U585I-IOT02A Board)
required connections not provided:
  Heap: 131072
connections are invalid

D:/examples/USB_Device1/Board/B-U585I-IOT02A/Board.clayer.yml (layer type: Board)