(PUP-2578) Unbreak services from packages which set local flags.

So don't add _flags="" for pkg_scripts if no :flags were set, as it
may override the default flags from inside the script.
(PUP-2578) Keep order for pkg_scripts.

Do not unconditionally alphabetically sort the list of pkg_scripts
as order matters. Explicit ordering will need to be forced through
resources dependencies.
(PUP-2578) Tweak #in_base? by not relying on pkg_info, but on /etc/rc.conf which is faster
(maint) Quote class name in init.pp template

According to the style guide:

All resource titles should be quoted. (Puppet supports unquoted resource
titles if they do not contain spaces or hyphens, but you should avoid
them in the interest of consistent look-and-feel.)

A class is a resource.
(PUP-2578) Adjust spec tests to recent changes:

- Ensure strict ordering of the result of #pkg_scripts_append
- Add test for #in_base?
- Ensure package scripts don't end up with empty flags
(maint) Remove resources_spec.rb Facter stubs

 - Facter stubs would actually cause different types to be created
   on Windows that would break tests.
 - Instead of creating stubs that affect a number of tests, carefully
   select the uid in the one test that needs to be particular about max
   UID
Merge pull request #2557 from jasperla/service

(PUP-2578) Adjustments for new OpenBSD service provider
(PUP-2738) Ensure block in user.password_is?

This ensures that a block is given by password_is? when calling
logon_user even though it doesn't need to do anything with it. We went this
route because it made more sense to require a block for this call versus
checking if a block was given in the logon_user method. If you call
logon_user without passing a block you cannot take the next step to later do
something as that user. So it would be a misleading if we allowed it without
requiring a block.
Merge pull request #2782 from ferventcoder/ticket/master/PUP-2738-fixes

(PUP-2738) Ensure block in user.password_is?
Merge pull request #2785 from Iristyle/maint/master/PUP-2454-uid-fix-Windows

(maint) Remove resources_spec.rb Facter stubs
(PUP-2557) Error on node inheritance

The future parser needs to be as close as possible to what will be the
default in Puppet 4. By making the node inheritance a warning instead of
an error, it makes it so that Puppet 4 will be significantly different
from puppet 3 with --parser future. This changes it so that both Puppet
4 and Puppet 3 with parser future will disallow node inheritance. The
error message is retained, which should provide good guidance whenever a
user does encounter this.

This change leaves all of the tests for node inheritance only working on
the --parser current. In addition an acceptance test that simply checked
variable scoping with an ENC has been converted to an integration test
along with all of the other tests about variable scope.
Merge pull request #2788 from zaphod42/issue/master/pup-2557-node-inherits-unsupported-in-future

(PUP-2557) Error on node inheritance
Merge pull request #2673 from roidelapluie/init_quote_class

(maint) Quote class name in init.pp template