##### SUMMARY
Mentioned modules should allow to select encoding for a file (defaulting to utf8 or utf16)
I have a requirement to generate simple files with ascii encoding. I can't do that with neither win_copy nor win_template

win_copy currently creates file with UTF16
##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME
win_copy
win_template

##### ADDITIONAL INFORMATION
Tested on WinSrv 2016, PS-5.1
```yaml
- name: Bootstraping
  hosts: all
  tasks:
    - name: Deploy file
      win_copy:
        content: 'text'
        dest: 'C:\some\path.txt'
```

variable_end_string:
    description:
      - The string marking the end of a print statement.
    type: str
    default: '}}'
    version_added: '2.4'
  trim_blocks:
    description:
      - If this is set to C(yes) the first newline after a block is removed (block, not variable tag!).
    type: bool
    default: no
    version_added: '2.4'
  force:
    description:
      - If C(yes), will replace the remote file when contents are different
        from the source.
      - If C(no), the file will only be transferred if the destination does
        not exist.
    type: bool
    default: yes
    version_added: '2.4'
notes:
  - Templates are loaded with C(trim_blocks=yes).
  - Beware fetching files from windows machines when creating templates
    because certain tools, such as Powershell ISE,  and regedit's export facility
    add a Byte Order Mark as the first character of the file, which can cause tracebacks.
  - To find Byte Order Marks in files, use C(Format-Hex <file> -Count 16) on Windows, and use C(od -a -t x1 -N 16 <file>) on Linux.
  - "Also, you can override jinja2 settings by adding a special header to template file.
    i.e. C(#jinja2:variable_start_string:'[%', variable_end_string:'%]', trim_blocks: no)
    which changes the variable interpolation markers to  [% var %] instead of  {{ var }}.