Configure vm.args via conform about conform

[bitwalker]

I would like to support this yes. I'd like some thoughts on the best approach to implementing this though, since we want a single source config file, but produce two output files. How do we indicate which mappings go to which file? It could be a mapping property which defines the output file, or perhaps we should have a special prefix key for vm.args mappings, such as erlang.vm.name = [email protected] which produces -name [email protected].

I'm not sure on what the best approach will be in order to keep things flexible in the future. I want to keep conform abstracted at the level of .conf. -> conversion/translation plugin (i.e. converts the parsed conf to Erlang config terms) -> output format generator (i.e. write datastructure as Erlang terms, or perhaps Elixir terms, or as a new conf format like vm.args, etc.).

Thoughts are welcome!