(Maint) dont fail on path unless absolutely required.

Previously, ensure=>running was required to specify the path. However,
if the zone is already configured, we dont really need the path.
This patch gets rid of that requirement.
- adds spec tests for start.
(Maint) - simplify methods in ZoneMultiConfigProperty (adds wrap).

This patch extracts the arrification into a single method wrap,
and shortens the method definitions by removing redundant code.
(Maint) Type Zone : fix formatting, comments

Add comment explaining why ensure:retrieve is necessary, added the output
of zone info to explain the regex, Fix format space, refactored global
retrieve to make it simple and succinct, simplify autorequire(:zfs),
setstatus, updated the regex in getconfig so that it matches the output
better. Updated the test case for getconfig
(#15886) Refactor state machine

The zone type has an internal statemachine that ensures that the state
transition is linear from configured -> installed -> running.
Previously, the state machine was intertwined with the code of zone
type. This commit extracts the statemachine so that thestatemachine is
in its own class

In order to remove future confusion, we also rename newvalue to seqvalue
and ensure that the newvalue is called from within the seqvalue. The
seqvalue is so named to indicate that the order of declaration of the
seqvalues determine the order of progression of states in the state machine.
Since we call parent newvalue from inside the seqvalue, we can now avoid using
munge which was added for this reason.

- Added test cases for fsm
(Maint) simplify line2hash, ensure iptype exclusive property is correct

Updated line2hash so that the method is succinct and simple, and added test cases for it.
(#15886) remove ZoneConfig and ZoneMultiConfig

Remove the zone specific properties from types, and move their handling to the provider.
This is done so that we can avoid stepping on the toes of puppet core and override methods
that have default behaviors except when necessary. The zone type is also more cleaned up
so that it can serve as a base for other container implementations.

Type: the properties that earlier relied on ZoneMultiConfigProperty are now moved to
Puppet::Property::List. The methods should and insync? are added to override the behaviors in
the parent methods. The should method in parent joins the array values together before
comparison. However, we do not want this behavior, and instead want it to remain as an array.
Hence we override should. We also override insync?  which uses should in parent for the same
reason.

Provider: the def_prop and def_multiprop now handles the definition of properties. They
add the methods prop(), prop=(), and prop_conf() to each properties that the provider provides.

The prop_conf() method is needed for getting the text to send to zonecfg on configure.
(#15886) getstatus should rename ip-type to iptype

previously, getstatus parsed the output of zonecfg info which contained
key `ip-type`. However, we are looking for the key `iptype`. this caused
the zone provider to not detect when iptype was changed, and always assume
the default value 'shared'. This commit gets the ip-type and assigns it to
iptype.
(#15886) commit the complete commands at the end.

Previously, the provider was applying the setconfig commands as soon as
it was called. This caused problems when the commands that were being called
needed to be called in a transactional manner
(i.e eth,exclusive -> eth:ip,shared). This uses flush to pass the required
commands at once through a pipe to zonecfg rather than do it one at a time.
(#15560) Refactor LogonUser

Previously, the ADSI utility code validated a user's password by
attempting a network logon session as that user. However, the ability to
create a logon session and use the resulting process token is something
that is generally useful, in say the next commit.

This commit refactors the call to `LogonUser`, adds a helper method for
checking the validity of a password, and modifies the ADSI code to call
it.

The call to `LogonUser` remains the same except that the MSDN docs say to
specify a '.' as the domain for local user accounts, and we null out the
token handle prior to calling LogonUser instead setting it to
"\x20\x20\x20\x20" which could be interpreted as a valid handle.
(#15560) Create the user's profile if managehome is true

Previously, specifying `managehome => true` on a user resource would have
no effect even though the Windows ADSI user provider claimed to support
the `manages_homedir` feature.

On Windows, a user's homedir (profile) is not created when the user
account is created, but when the user logs in for the first time. As
a result, if Puppet created the user account, and then tried to apply
another resource that depended on the existence of the user's home
directory, such as ssh keys, then Puppet would fail.

This commit changes the Windows ADSI user provider such that if
`managehome` is enabled, then it will load and unload the user's profile.
This will create the profile if necessary and apply the appropriate DACL
to the profile and subdirectories.

This commit follows the Microsoft recommended way of creating a user
profile: http://support.microsoft.com/kb/196070/en-us
(maint) commit the complete commands at the end.

The provider.flush() comamnd was missing.
(#15560) Delete user's profile after deleting account

Previously, if Puppet deleted a user account and `managehome` was true,
then Puppet would leave behind the user profile on disk, e.g.
C:\Users\%USERNAME%.

In keeping with the semantics of the `manage_homedir` feature, this commit
modifies the Windows ADSI user provider to delete the user profile when
`managehome` is true.

On systems before Vista SP1, the Win32_UserProfile class does not exist.
Worse, there is no reliable and built-in way to delete user profiles.
There is the widely used delprof.exe utility included in the 2003 Resource
Kit, but it's not part of the core OS and it doesn't work in later
versions of Windows.

As a result, the Windows ADSI provider will make a best effort to delete
the user profile, and that should work on Vista SP1 and later systems. On
earlier systems, we will warn that it's not supported.

This commit also adds an acceptance test to verify the home directory
gets created, and deleted (on systems that support it).
Merge pull request #1077 from vrthra/ticket/3.x/15886_refactor_zones

(#15886) refactor zones
Merge pull request #1094 from vrthra/ticket/3.x/15886_refactor_zones

(maint) commit the complete commands at the end.
Merge pull request #1088 from joshcooper/ticket/2.7.x/15560-managehome-windows

(#15560) Implement manages_homedir semantics on Windows
Merge branch '2.7.x' into 3.x

* 2.7.x:
  (#15560) Delete user's profile after deleting account
  (#15560) Create the user's profile if managehome is true
  (#15560) Refactor LogonUser
(#16175) Touch filebuckets contents when we get a new path

Touch the contents file when we get a new path for the file. This
simplifies cleanup scripts for deleting old filebucket files for
example.
Merge branch 'feature/3.x/16175-update-modification-time-on-filebucket-contents' into 3.x
Merge remote-tracking branch 'origin/3.x'
Merge remote-tracking branch 'upstream/master'