Simplify ESDL connection to Tulipa flows, and back

[suvayu]

In ESDL 2 assets are connected via a transport asset, whereas Tulipa prefers direct connection between assets due to efficiency reasons. We need to find:

• Strategy to simplify ESDL connections to Tulipa flows #4
• Associate profiles to assets & flows #6
• vice versa, i.e. going from a Tulipa flow to a connection in ESDL using transport asset. (deal with this later)

[clizbe]

I think the first step is determining what data Tulipa needs for the connection and where that data can be entered in the MapEditor.

[suvayu]

For now I implemented what @datejada suggested here: #1 (comment)

Code wise, it's this:

esdl4tulipa/src/esdl4tulipa/mapping.py

Lines 67 to 71 in 8bb5021

	@dataclass(unsafe_hash=True)
	class _producer_t(AssetData): # noqa: D101
	investment_cost: float | None = None
	variable_cost: float | None = None
	lifetime: float | None = None

esdl4tulipa/src/esdl4tulipa/mapping.py

Lines 135 to 140 in 8bb5021

	@dataclass(unsafe_hash=True)
	class flow_t(_producer_t): # noqa: D101
	from_asset: str = ""
	to_asset: str = ""
	capacity: float | None = None
	efficiency: float | None = None

The attributes you see above are the Tulipa names, and the ESDL names are recorded in the esdl_key method (click the links aobve). Essentially I skipped anything for which we haven't associated an ESDL attribute in the table in #1