Changing calling syntax of copy and template module to be key-value based

I think the command module is the only module that should not be key-value, so looking at changing a few modules before we get too far ahead

The template module may want to write a file and also specify permissions, so I’m proposing we move things to be more like:

copy src=/path dest=/path

AND

template src=/path dest=/path

This will also break ground for the template module to take an optional list to the variable source file, ex:

template src=/path dest=/path metadata=/path/to/file.json

Allowing for non root templating and such, which is a bug I’ve filed based on Jeremy’s suggestion that most things be doable as non-root (and I totally agree).

I’m going to make this so and update the playbook example to follow. I’m also going to start on the docs for command modules shortly, which will go in manpage section 5 (I guess).

–Michael