Initial sketch of manifest-based naming and multi A2L

[pmai]

No description provided.

[t-sommer]

Proposal for the XML from my discussion with @pmai:

<fmiLayeredStandardManifest
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="../../schema/fmi3LayeredStandardXcpManifest.xsd"
    xmlns:fmi-ls="http://fmi-standard.org/fmi-ls-manifest"
    fmi-ls:fmi-ls-name="org.fmi-standard.fmi-ls-xcp"
    fmi-ls:fmi-ls-version="1.0.0-rc.4"
    fmi-ls:fmi-ls-description="Layered standard based on FMI 2.0 and FMI 3.0 for describing and implementing XCP support for FMUs, which can either provide an XCP service or allow direct memory access via A2L files.">
    
    <Interface containsXCPService="true" supportsDirectMemoryAccessViaA2L="true" definition="vECU.a2l" description="Lorem ipsum...">
        <Variable name="ENABLE_TCP" role="EnableXCPOverTCP"/>
        <Variable name="ENABLE_UDP" role="EnableXCPOverUDP"/>
    </Interface>

</fmiLayeredStandardManifest>

Actual path for binary A2L: /extras/org.fmi-standard.fmi-ls-xcp/<platform-tuple>/<definition>.

[pmai]

The broader refactoring can be found in #81, which can be discussed separately to this more conservative approach.

[chrbertsch]

Closed in favor of #81 after poll