Memory and threads setting may not be respected

[hinerm]

See this comment

[hinerm]

In jaunch, we would list ImageJ.cfg as one of the config files that we read (to get the variables) and then fiji.toml would use the memory and threads setting

[hinerm]

Actually the ImageJ.cfg is not in a K:V format.

So we could support (regex?) mechanisms for parsing non-K:V lines to a K:V format (e.g. launch configuration flags would map to K:V pairs)

We're still brainstorming the right way to handle this

[hinerm]

See fiji/fiji#351 for a possible direct solution