Prior to this commit, we set a default timeout of 20 minutes for the dsc
type, and this was not configurable.

This change adds a new "dsc_timeout" param to the dsc type, which
accepts an integer value for the number of seconds execution should wait
before exiting.

Users can now configure this timeout through their manifests, same as
you would with any other property see below:
```
dsc { "Running Script":
  resource_name => 'Script',
  module        => 'PSDesiredStateConfiguration',
  dsc_timeout   => 10,
  properties    => {
    getscript  => 'Start-Sleep -Seconds 5',
    testscript => '$false',
    setscript  => 'Start-Sleep -Seconds 5',
  },
}
```

…eout

(CAT-1869) - Add configurable dsc_timeout param for dsc type

…eout

(maint) - Implement retries for timeout test

(maint) Update labeller.yml to pull_request

Revert "(maint) Update labeller.yml to pull_request"

pdksync - (CAT-1954) Remove labeller

(CAT-1927) - Remove Windows 7, 8.x and 2008 R2 Support

This commit adds a warning the readme about the use
of sensitive data with script block logging enabled.
As per microsoft's own recommendation, protected event
logging should also be enabled to encyrpt this data.

(maint) - add disclaimer for script block logging

Ths commit fixes the timeout matcher to more accurately match a
legitimate dsc timeout. Before, if output was nil for any other reason
dsc_lite would assume timeout which is not strictly correct. There is a
specific error message returned on dsc timeout which we should strive to
match instead.

Additionally, moved the logic to only execute for nodes with windows
powershell support as we can only pass a timeout to powershell on these
nodes.

(Bug) - Fix timeout matcher

Release prep v4.1.0