maint: Refactor mount specs

Reduce the number of describe blocks and use real object instances
instead of mocks. This way it should be easier to extend the specs in
the future
(6409) Reject spaces in mount type

The puppet mount provider is unable to handle fstab entries with spaces
so it should not try to write such entries.

The accepted solution in redmine ticket #6409 is for the mount type to
reject property values that contain spaces.
(#6409) Dont use invalid values in type_spec

The type_spec uses the mount type as an example in a lot of spec tests.
Unfortunately it uses example values that are now invalid for the mount
type.

The atboot property only accepts :yes and :no now, because these are the
only valid options in /etc/vfstab [1].

[1] http://docs.oracle.com/cd/E19455-01/805-7228/6j6q7uev3/index.html
(#4689) Set correct blockdevice for nfs mounts

Solaris vfstab has an extra field "blockdevice". The Puppet
Documentation claims that the blockdevice should default to the correct
value and you do not have to set it explicitly. While this may be true
for regular devices the user has to set blockdevice explicitly if the
mount resource describes an NFS share.

The correct entry for NFS shares in /etc/vfstab is to set blockdevice
to "-"
(#6793) Remove trailing slashes from mount resource

The mount system command always displays mount points without trailing
slashes so if a user defines a mount resource with a trailing slash,
puppet will always see the mount resource as unmounted and as a result
will keep remounting the device on every puppet run.

Munge the name and strip away any trailing slashes but make sure that we
do not remove the slash if the mount describes the root directory `/`.
This way the munged name will always equal the mount output and puppet
is able to find it.
(#21168) Set default pass property to "-" on Solaris

The current default value of "0" for the pass property has a different
meaning on Solaris than on other systems. A value of 0 actually depends
on the filesystem type: It will cause the system to not fsck the device
if it is an UFS filesystems and will fsck the device if it is not an UFS
filesystem

(http://docs.oracle.com/cd/E19455-01/805-6331/fsadm-59727/index.html)

I never actually saw a value of "0" in any /etc/vfstab and it seems to
be common to use "-" instead. This will always deactivate filesystem
checking and is also used in many examples (see link above).

Change the default value of the pass property to "-" on Solaris and keep
the default value of zero on other systems.
(#15837) Do not pass options explicitly when mounting

The mount provider explicitly passes the mountoptions to the mount
command with the "-o" parameter. While this works in most cases it fails
when the option property contains an option that needs to be unique as
the default behaviour of the mount command seems to be to merge fstab
options with explicitly definied options via the commandline.

Since the mountprovider always updates the /etc/fstab file before
attempting to mount we should not need to pass the options explicitly.
The current code mentions some weired behaviour on MacOSX so we keep the
original behaviour on MacOS and drop the explicit options on
all other platforms.

This also fixes #7791
Merge pull request #1699 from stschulte/ticket/master/mount_fixes

Various mount fixes