Use some unique task names for windows_task functional tests
Use some unique task names for windows_task functional tests

The 2008r2 tester has been failing with an error like:

```
  1) Chef::Resource::WindowsTask action :enable enables the disabled task
     Failure/Error: expect(current_resource.task.status).to eq("not scheduled")

       expected: "not scheduled"
            got: "running"

       (compared using ==)
     # ./spec/functional/resource/windows_task_spec.rb:1481:in `block (3 levels) in <top (required)>'
```

This has only been happening on the enable and disable tests and appears to be a timing issue. This change gives thoses tests unique names and changes the default name to not be 'chef-client' which is more likely to collide with another test.

This change has passed chef-test on jenkins in an ad-hoc test.

Signed-off-by: Bryan McLellan <9da9e2973b9c72b95f1bc7169993146760fceeb1@loftninjas.org>

MsysTechnologiesllc/chef,mattray/chef,MsysTechnologiesllc/chef,tas50/chef-1,gene1wood/chef,Tensibai/chef,gene1wood/chef,juliandunn/chef,nvwls/chef,juliandunn/chef,Tensibai/chef,higanworks/chef,martinisoft/chef,tas50/chef-1,jaymzh/chef,mwrock/chef,chef/chef,mwrock/chef,tomdoherty/chef,nvwls/chef,mattray/chef,juliandunn/chef,Ppjet6/chef,gene1wood/chef,Ppjet6/chef,mattray/chef,nvwls/chef,jaymzh/chef,martinisoft/chef,MsysTechnologiesllc/chef,Ppjet6/chef,higanworks/chef,higanworks/chef,tomdoherty/chef,nvwls/chef,nvwls/chef,juliandunn/chef,tas50/chef-1,higanworks/chef,tomdoherty/chef,jaymzh/chef,tas50/chef-1,higanworks/chef,mwrock/chef,martinisoft/chef,Tensibai/chef,chef/chef,MsysTechnologiesllc/chef,tomdoherty/chef,martinisoft/chef,Ppjet6/chef,nvwls/chef,mattray/chef,Tensibai/chef,Ppjet6/chef,chef/chef,Ppjet6/chef,chef/chef,juliandunn/chef,tomdoherty/chef,jaymzh/chef,gene1wood/chef,mwrock/chef,mattray/chef,martinisoft/chef,Tensibai/chef