Add aux flows to topology

[olejandro]

This PR adds aux commodity flows to topology. It also expands the list of Veda aliases for TIMES attributes.

[olejandro]

@siddharth-krishna this one has regression with respect to addtional rows, so still needs some work.
Btw, was wondering whether this pattern where we are looping through the dictionary searching for a key is efficient? Please feel free to modify...

[Antti-L]

@olejandro

Expand aliases_by_attr

Just a small question/comment about this alias matter: I wonder whether you take into account that there are both strict aliases and variants of parameters now included in the lists. For example, CF is not strictly an alias for NCAP_AF, because the default LimType for CF (alias UTILIZATION) is FX while it is UP for NCAP_AF (alias AF, AVAILABILITY). A few other examples are EFF, which is not a strict alias for ACT_EFF, but a variant which does not support specifying the CG in ACT_EFF at all, and COST, which is not a strict alias for IRE_PRICE, but a variant which does not support specifying the commodity or IE, and ENV_ACT, which is not strictly an alias for FLO_EMIS, but a variant which does not support specifying the source CG.

[olejandro]

@Antti-L good point! Yes, we already include a dictionary that specifies (some of) those defaults (incl. whether it should be input or output commodity like for share-o vs share-i). The idea is to move this info to a separate file, so that it is easy to get an overview and modify it. I'll make sure to tag you in that PR, so you can comment on it.

[olejandro]

@siddharth-krishna there is one additional record on Ireland which I believe is okay to keep. :-)

[siddharth-krishna]

Sounds good. Let me think what's the best way to merge this PR with a failing check..

[olejandro]

@siddharth-krishna I was thinking to temporarily change the repository settings to be able to do this (i.e. not to enforce restrictions for admins).

[siddharth-krishna]

Sounds good!