Merge remote-tracking branch 'upstream/stable'

* upstream/stable:
  Docs: Clarify descriptions of "ordering" and "report_serialization_format" settings
  (#22375) Don't echo the backed up file to the caller
  (#22375) Prefer raw-like serialization format
Merge pull request #1861 from badgerious/fix/master/22258_failed_execs

(#22258) Create new console for each puppet run
(#22258) Create new console for each puppet run

Powershell apparently has some issue trying to share the Windows
service's console when running under ruby.exe (as opposed to rubyw.exe).
This patch causes the service to create a new console for each puppet
child it kicks off, which resolves the issue.
Merge branch 'ticket/stable/22258-create-new-console' into stable

* ticket/stable/22258-create-new-console:
  (#22258) Create new console for each puppet run
(#22110) Documentation improvements per GH review

* Note that both POST and GET are supported with some historical
  context around the introduction of POST
* Note that the response is an example, and remove the mid-example
  comments, so that the example is cleaner
Merge remote-tracking branch 'upstream/stable'

* upstream/stable:
  (#22258) Create new console for each puppet run
(#22383) Allow all boolean values for atboot

The previous restrictions placed on the atboot property for mount caused
some previously valid manifests to begin to fail. The problem stems from
the fact that atboot is only used on solaris, but can always be
specified by users. It used to be able to be nearly anything, but only
yes and no meant anything on solaris. This fixes the problem by
expanding the allowed values to include all of the "boolean" values as
expressed in the Puppet::[Parameter|Property]::Boolean type and using a
munge method to convert the boolean to the correct yes or no value.
Merge pull request #1862 from kylog/issue/22110-document-catalog

(#22110) document catalog endpoint
Merge pull request #1879 from zaphod42/issue/stable/22383-mount-no-longer-allows-true-for-atboot

(#22383) Allow all boolean values for atboot
Merge branch 'stable'
(maint) Windows failing spec fixes

 - The usage of Dir.getwd in tests has been simplified to
   File.expand_path to properly handle mixed case CWD
 - util_spec.rb ensures 'FOO' Env var cleared before test starts
 - Windows SID checks should be performed as a regex match to
    properly handle all accounts starting with S-1-5-*, which denotes
    accounts with an identifier authority of SECURITY_NT_AUTHORITY
    instead of hardcoding S-1-5-32-544, the Administrators group
(#22362) Changes in const_defined?() on ruby 1.9 break Puppet::Util::Classgen
Merge pull request #1871 from joshcooper/ticket/master/21133-report_windows_package_version

(#21133) Report on installed windows package versions
(maint) ignore Gemfile.local
Merge pull request #1885 from ferventcoder/stable

(maint) ignore Gemfile.local
(packaging) Update PUPPETVERSION for 3.3.0-rc3
Merge branch 'stable'

* stable:
  (packaging) Update PUPPETVERSION for 3.3.0-rc3
  (maint) ignore Gemfile.local
(#8040) Test order of application for contained classes

This also includes some minor refactoring of the contain function.
(maint) Fix output of ArithmeticExpression label (future parser)

If an ArithmeticExpression is involved in an error and a label
is output as part of the error message this led to an internal
error - undefined o_operator.

This fixes the problem (it should have been o.operator).
(#22442) Fix problem with missing issue ILLEGAL_NAME (future parser)

When a qualified name did not conform to the naming rule for
qualified names a reference was made to an undefined issue.

There was also a problem with the name validation rule as it was not
anchored at the beginning of the matched text. It thus allowed
variable names like `$Aaa` (which should also have been flagged as 
an error). Other naming validation patterns suffered from the same
problem.