winPB: Stop using ansible.windows as prefix to tasks
The Windows playbooks are not currently able to run using the setup process for running our windows docker containers as they fail with a ERROR! no action detected in task message when we try to run them using the ansible supplied with a default cygwin install. The implementatino of fully qualifications were done under:
- https://github.com/adoptium/infrastructure/pull/3726
- https://github.com/adoptium/infrastructure/pull/3774
I've got a feeling there was a reason we did this but I'm not sure what it is and it's currently causing me a problem, so I'd like to remove the full qualification for now, unless there is another simple solution.
NOTE: Up til now we've been using a fixed version of the playbooks as specified in https://github.com/adoptium/infrastructure/blob/e23e780a20b920e576291283d6229e11bb0d5603/ansible/docker/Dockerfile.win2022#L49 to create the containers. This branch (which has now been merged) did not have the above two PRs so hasn't been causing a problem. This error was found while attempting to bring that up to date so we can use the master branch going forward. Also noting that there is one other issue relating to the ant-contrib download being unreliable that will also need to be addressed - I've worked around that in another branch for now.
Checklist
- [ ] commit message has one of the standard prefixes
- [ ] faq.md updated if appropriate
- [ ] other documentation is changed or added (if applicable)
- [x] playbook changes run through VPC or QPC (if you have access) https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/2014/
- [ ] VPC/QPC not applicable for this PR
- [ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly