Release mergeback 2.2.0

Previously the spec tests were failing on Windows due to linux paths being used
on a Windows platform.  This commit branches the test to use a correct absolute
path depending on the type of platform that's actually running the test.  This
is required as some functions within Puppet cannot be mocked correctly, such
as path validation.

Previously three ruby files in the spec unit and functions directories had the
hash-bang prefix set to run these files using ruby. As these are rspec or rspec
helper files, these would not be directly invoked via ruby anyway.  The rubocop
rule Lint\ScriptPermission gets confused on Windows as this is unix convention.

(maint) Fix spec tests on Windows

inifile readme cleanup

There was a bug in Puppet <= 5.4.0 where values of attributes could never be false. If set to false, they would actually just be nil, or they would be true. This has been fixed in 5.5.0 and requires the applied change in this module. @resource[:refreshonly] will no longer be set to nil, so only checking for its existence is not enough. Instead, also check to make sure it is not :false

(MODULES-6687) puppet bug fixed

Instead of trying to anticipate output in the validation step, this makes sure the param is turned into a boolean value before validation.

(MODULES-6687) actually fix refreshonly issue

…form.windows?

Puppet::Util::Platform.windows? is the preferred check and is already in
use by rspec-puppet.

rspec-puppet currently prohibits the use of structured facts for
'pretending' to be windows. this changes the failing test to use
'osfamily' instead of ['os']['family'] so that it passes while a
[PR](rodjek/rspec-puppet#675) is being reviewed.

(MODULES-6723) release prep for 2.2.1 and workaround for spec test

* inifile readme edits

* Update README.markdown