(packaging) Update PUPPETVERSION to 3.4.0-rc2
Maint: Adjust wording and formatting of several settings, notably reports
(#23403) 'autosign' setting should manage file parameters

Puppet settings of type :file can specify the owner, group, and mode of
the file specified by the setting, like so:

    [master]
    autosign = $confdir/autosign.conf { mode = 664, owner = service, group = service}

Commit bca628dc extracted the autosign setting validation to a setting
class but dropped the ability for file settings to be specified. This
commit resolves the issue by making the autosign setting inherit from
the file setting.
Maint/22374: Clarify the action/interaction of the noop setting and metaparameter
(#23403) Do File.expand_path on the expected path

The FileSetting#to_resource method will call File.expand_path, which on
Windows, will convert a relative path like /foo/bar to an absolute path based
on the current drive.

This commit changes to the test so that the autoconf setting returns an
absolute path.
Merge branch 'pr/2150' into stable

* pr/2150:
  (#23403) Do File.expand_path on the expected path
  (#23403) 'autosign' setting should manage file parameters
Merge pull request #2151 from nfagerlund/docs_noop_clarity

Clarify noop docs, reformat some other settings
(maint) Pin beaker to 1.2.0
(Maint) Move to newer beaker

rbvmomi released a 1.8.0 that broke ruby 1.8 compatibility. We tried
pinning to an older beaker, but that wouldn't have worked because of the
way beaker depends on rbvmomi. Beaker 1.3.1 pins itself to an rbvmomi
that we should be able to use and so using 1.3.1 should solve the issue.
(packaging) Update PUPPETVERSION to 3.4.0
Merge tag '3.4.0' into stable

3.4.0

* tag '3.4.0':
  (packaging) Update PUPPETVERSION to 3.4.0