Add unit test for verifying requirements installation to declared venv

modulesync 7.0.0

Add # frozen_string_literal: true required by rubocop check

https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/puppet/functions/stdlib/ensure_packages.rb#L36-L37

See https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/puppet/functions/stdlib/ensure_packages.rb#L36-L37

…is true

Just like we can skip managing the pip and venv packages, allow to
opt-out of managing the dev package.

Enforcing a state of these packages sometimes cause trouble if the user
of the module does not care about them but they get installed as another
package dependency (e.g. syslog-ng-mod-python depends on python-venv, by
default python-venv is ensured absent, so on each run Puppet wants to
install syslog-ng-mod-python (which install python-venv as a dependency)
or remove python-venv (which remove syslog-ng-mod-python as a
dependency)).  This can be avoided using the corresponding
`manage_XXX_package` paramater, but `manage_dev_package` was missing.

If user declares their requirements.txt in Puppet, don't skip pip installation in python::requirements

FreeBSD does not have a 'root' group.  System files owned by the 'root'
user belong to the 'wheel' group, so use that group by default.

This allow to use python::pip without the need to explicitly set the
`group` parameter to avoid the error:

> Error: Could not execute posix command: Invalid group: root

Bump puppet-epel to allow 5.x

Allow to skip management of python dev package

…9 to metadata.json operatingsystem_support array

apply python-venv exclude to RedHat family instead of just CentOS

Add Ubuntu 22.04 support

Add Debian 12 support

Release 7.1.0