Multiple list-like settings should get merged instead of overriding each other

[RReverser]

While working on .NET stuff, we noticed that currently having multiple -sEXPORTED_FUNCTIONS means that whichever is last, wins, which is not great when you want to pass an export file generated by tooling + statically some extra functions that need to be always exported. For example, if you specify:

-s EXPORTED_FUNCTIONS=@some.exports -s EXPORTED_FUNCTIONS=_OneMoreExport

Then today only OneMoreExport will end up exported and file ignored; if you change the order, the opposite happens.

It would be more useful for them to get merged instead. While chatting to @sbc100 about this idea, he suggested that the same should probably apply to other list-like settings too, e.g. ASYNCIFY_IMPORTS.

[sbc100]

I think we have considered this in the past (things might even have worked this way in the past). I can't think of any reason not to do this .. I would imagine we should do it consistently for all list-taking arguments.