Suppress misleading warn. in openbsd provider

I have observed that `pkginfo` command used as `listcmd` by `ports`
package provider sometimes outputs extra messages to stdout (the message
starts with `Updating the pkgdb`). This causes puppet to issue its own
warning as the line obtained from `listcmd` is not a valid package name.

This patch suppresses this spurious message.
Maint: Be more clear that puppet queue is deprecated

- Remove link to old wiki docs
- Link to PuppetDB docs
- Say "deprecated" again
Maint: (#18294) Update docs for ip property of Zone type (allows defrouters since 2.6)

Per Redmine 18294, the Zone type has allowed specifying default routers as part
of the IP string since at least 2.6 -- see Redmine 4296 for deets. This commit
updates the doc string to show how to do that.
Maint: Move pkgdmg documentation into provider description; document changed behavior

This wiki page was more longwinded than it needed to be; you can really sum it
up in about four bullet points. So I did that, and removed the wiki link.

Also, while investigating what the wiki said, it became clear that this provider
no longer actually uses open-uri: a Kernel.open call was changed to File.open,
but apparently nobody was using file:/// URLs (or anything weirder), so it went
unnoticed. So I added some comments for future maintainers of this code.
Maint: Remove remaining links to wiki pages in Puppet source

These pages now all have better-maintained counterparts in the main docs site.
Maint: Update docs for schedule type and metaparameter

The wording of these was out of date and somewhat strange.
Maint: Improve/reduce documentation of relationship metaparemeters

These descriptions were too wordy and too inconsistent. I'm imposing a format on
them so they all look alike, and a casual reader can tell how many there are and
how their behaviors differ. I'm also adding links to the more detailed
documentation.
Maint: Standardize docs for refresh behavior in resource types; clarify exec docs

Service/mount/exec already documented that they do the refresh thing, but it
wasn't organized in a predictable way. I'm imposing a convention of a bold
"Refresh" label, a reminder of where events come from, and a description of what
that type does when it gets one.

This commit also adds a lot more detail on how execs respond to refresh, since
it's actually really complicated and not the least bit intuitive. I also reworded
some of the older language near the top of the exec type, while I was in there.
Maint: Clarify docs for stage type and metaparameter

This was pretty disorganized and confusing. Now it's less so!
(#16570) Don't load the node object again in configurer

Avoid loading the node object again if we already have a catalog.
(PUP-1218) Add ssh-ed25519 support to the sshkey type
(PUP-1218) Teach the ssh_authorized_key provider about ssh-ed25519 too.
Bug 1051 (platforms mistook for versions)

Fix bug PUP-1051 by stripping out the extraneous platform info from the individual versions of the gems.
(maint) cron: Make the munge method for the command property more readable

The removal of leading and trailing spaces in cron commands was
performed using a perlism instead of just using String#strip.
Do that instead.
(PUP-1051) Add rspec test to verify fix
(main) Remove symlinks from acceptance harness

Git's cross platform handling of symlinks is problematic on windows, and
the symlinks are also causing problems in third party software like
Eclipse.  This commit removes them, and instead is explicit about which
pre-suite steps are executed, in what order, in the
config/{git,packages}/options.rb files.
Revert "Merge pull request #2207 from jpartlow/maint/master/simplify-confine-for-6857-test"

This reverts commit 6ad16a47f878df3eb3a31c063bff3e0f5c63745b, reversing
changes made to 2f1bee412b41cd2b244da39883f3a08a37aef1a3.
(PUP-724,#21922) Autoload compares only integer secs

Although the ultimate reasons have not been tracked down, there have
been occasions where the Puppet::Util::Autoload.changed? method will
erroneously report that a file has changed based on an mtime having
seemed to change nsecs, despite no evidence of this being seen in the
file system.

The previous implementation was comparing mtime (Ruby Time instances)
and the nsecs seem to be volatile under unknown conditions. When it does
break, this was manifesting as a failure to autoload
puppet/util/instrumentation/listeners/log.rb (the instrumentation code
is relying on Puppet::Util::Autoload for initial loading but does not
expect its listeners to be reloaded, and they are not written in such a
way as to be reloadable...) (see PUP-724 and its associated tickets for
details).

The work around is to instead just compare integer secs.
Merge pull request #2214 from jpartlow/issue/master/pup-724-autoload-mtime-test

(PUP-724,#21922) Autoload compares only integer secs
(maint) Update fedora platform designation for ticket_6857 test

Our config/nodes platform strings have changed and now read 'fedora'
rather than 'fc-' so ticket_6857_password-disclosure-when-changing...
needed to be updated to perform the ruby-libshadow test on fedora again.

Also providing the libshadow test output so we can see a little better
what's going on the next time this needs debugging.