Handling multiple feature models in the rendered overview

[vulder]

Currently, our build of the overview crashes when the feature model is not named FeatureModel.xml.

https://github.com/se-sic/ConfigurableSystems/actions/runs/5331473648/jobs/9659366282

[ChristianKaltenecker]

Hmmm. I guess this is the first case where we have feature models of multiple different versions (see Linux).
What could be the best solution here? I can rename the models to FeatureModel.xml, but I want to somehow keep the information about the version.
Creating multiple different directories (i.e., 'Linux-5.16' and 'Linux-6.2.1') would fix the issue, but won't work on long term if we expect further feature models from the same system but of different versions.
@s9latimm any thoughts on this?

[vulder]

I think renaming and duplicated folders will not help us. We probably need a fix for the process to build multiple models. Simplified with the name FeatureModel_DETAIL.xml maybe? So, we can easily match out the DETAIL part with an regrex, or ignore it with a glob.

Especially, for models, such as linux, it's worth while to keep multiple versions around.