##### 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'
```

description:
    - Determine when the file is being transferred if the destination already exists.
    - When set to C(yes), replace the remote file when contents are different than the source.
    - When set to C(no), the file will only be transferred if the destination does not exist.
    type: bool
    default: yes
  follow:
    description:
    - Determine whether symbolic links should be followed.
    - When set to C(yes) symbolic links will be followed, if they exist.
    - When set to C(no) symbolic links will not be followed.
    - Previous to Ansible 2.4, this was hardcoded as C(yes).
    type: bool
    default: no
    version_added: '2.4'
  output_encoding:
    description:
    - Overrides the encoding used to write the template file defined by C(dest).
    - It defaults to C(utf-8), but any encoding supported by python can be used.
    - The source template file must always be encoded using C(utf-8), for homogeneity.
    type: str
    default: utf-8
    version_added: '2.7'
notes:
- Including a string that uses a date in the template will result in the template being marked 'changed' each time.
- Since Ansible 0.9, templates are loaded with C(trim_blocks=True).
- >
  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: False)
  which changes the variable interpolation markers to C([% var %]) instead of C({{ var }}).