Pin fog-vsphere to >= 3.6.4

See https://community.theforeman.org/t/problem-with-end-build-on-vmware-esxi-8-0-u2/37139

Fixes #37092 - Use minitest_reporters_github in GHA

This is a specialized reporter to provide GitHub annotations on failure.
These annotations can be seen in the changes files tab.

Fixes #37093 - Drop single_test gem

The rails command (bin/rails test) provides mechanisms to run individual
tests while the last commit to single_test was 7 years ago.

Fixes #36936 - Switch to terser

Fixes #36819 - Bump sidekiq to at least 6.5

Fixes #36651 - Support Minitest 5.19+

• This reverts commit 1c3a4155f286352e0abbf0d0b298e47e81c2d6c5.
  Thus un-pinning minitest again
• update minitest-spec-rails to 7.1+
  This contains a fix required for minitest 5.19+
• Update mocha to 2.1+ for minitest 5.19+ compat...

update shoulda-matchers to 5.x

we had it pinned to <4.4 as 4.4 had a bug, but that is fixed since 4.4.1
and we really should update to the next major version

Fixes #36617 - Pin minitest < 5.19 to resolve test failures

Refs #36518 - bump fog-vsphere version

Fixes #36330 - Fix plugin translations in frontend

- Add plugin:po_to_json rake task
- Load js locale files for all plugins
- Make i18n.js do multi-domain lookup

Fixes #36357 - allow Puma 6.x

Fixes #36262 - allow newer prometheus-client gem

While there were breaking changes, none of them affect us, so let's just
allow the new versions.

Fixes #35862 - Update fog-vsphere version in Foreman

Fixes #35088 - Remove GCE Compute resource code

All code related to GCE compute resource
is now in Foreman Google plugin

https://github.com/theforeman/foreman_google

Refs #35414 - Add sd_notify dependency to service

Puma has a soft dependency on sd_notify when systemd is used. In our
service we use this so we should make sure it's pulled in. Prior to
9b0652fed9f86fd429e237ce359422a1dba14a2a the dynflow_sidekiq group
pulled it in, which technically wasn't entirely correct but in practice...

Fixes #35414 - Drop sd_notify usage

Sidekiq should be doing this on its own behind the scenes

Fixes #35414 - Bump Sidekiq to 6.3.z

As a side effect, gitlab-sidekiq-fetcher should get updated to >= 7.1.0.

Currently latest sidekiq is 6.5.5, but anything above 6.4.0 is rather
verbose about things being deprecated in sidekiq 7.0.0.

Similarly, latest redis is 4.8.0, but anything above 4.5.0 is rather...

Fixes #35430 - Update as_deprecations_tracker for Ruby 3

Fixes #35371 - Update show_me_the_cookies to 6.x

This version brings compatibility with rack-test 2.x.

Fixes: a439e1e92e9f98f3dbc8ed2f204bd53cc861565e

Fixes #35244 - Pin Faraday to 1.x

While Foreman doesn't depend on Faraday directly, it is pulled in via
fog-google which depends on google-cloud-env, googleauth and signet
which all pull in Faraday. This is not a bad thing, but our ecosystem is
largely incompatible with Faraday 2.x. Pinning to 1.x makes packaging...

Fixes #35146 - Lock rack-test < 2.0.0 (#9288)

Fixes #32686 - use fog-google 1.14+, compatible with Ruby 3.0

fog-google 1.13 started announcing 3.0 compatibility in the gem spec,
but 1.14 contains bug fixes to actually make it work

Remove duplicate puma gem declaration

This duplication doesn't show up in production, but in development and
testing it does. By declaring it in service.rb for both groups it will
still be included in both production setups and testing.

According to 36d17b1743569158e1a68d323e7222fa04168c0f puma is needed in...

Fixes #34058 - extract multiline string for translation

Fixes #22110 - allow minitest 5.11 and newer

Fixes #26968 - Switch to minitest-reporters

ci_reporter_minitest is unmaintained and since minitest 5.1 it no longer
shows the class names. minitest-reporters does.

Refs #27906 - Add FacterDB test

It should be noted that these tests are fairly slow. On my system they
add a minute of runtime to the tests.

Fixes #29481 - unpin capybara

Old capybara doesn't play well with new selenium-webdriver.
The pin is already few years old, we should not keep it anymore.

Fixes #33098 - update fog-libvirt to 0.9.0

Fixes #32193 - enable byebug in development

Fixes #22259 - bump fog-libvirt

Fixes #30835 - ovirt Filter SD by data and volume

Fixes #31431 - Update to Puma ~> 5.1

Puma 5.1 introduced a feature to synthesize binds for systemd activated
sockets. This removes the need to duplicate the FOREMAN_BIND in two
places (foreman.socket and foreman.service).

puma-plugin-systemd is no longer needed since Puma 5.1 gained native...

Fixes #30793 - Remove API v3 from fog-ovirt

Fixes #30889 - random unitialized constants failures

This new fog-vsphere release mainly contains a fix for sporadic unitialized constant failures.
Most likely caused by wrong autoloading in the gem namespaces.
The new release should fix it and we should get that release in as soon as possible.

Fixes #30925 - use the organization style gem

Use `theforeman-rubocop` gem to share common RuboCop rules with plugins.
It serves as base for our rubocop styles and rules.

Fixes #28484 - Pass hostname to GCP API

Fixes #31090 - drop poltergeist dependency

In 475cdc34 we've stopped using poltergeist for integration testing.
We have forgotten to drop the dependencies.
We were still installing and requiring it in Jenkins.

Fixes #30916 - pin puma to < 5.0

Fixes #30730 - Implement systemd notify support for dynflow-sidekiq

Fixes #29356: Use puma-plugin-systemd to provide systemd notify support

This points to a fork of puma-plugin-systemd maintained by theforeman
organization to ensure this works with Puma 4.

Fixes #30712 - pin shoulda_matcher < 4.4

Fixes #28226 - upgrade to sprockets 4

Fixes #29936 - Bump fog-aws version to 3.6.5

Fixes #29716,#29283 - Bump fog-ovirt version

Fixes #29870 - replace awesome_print with amazing_print

Refs #28874 - bump fog version

Fixes #29679 - Require fixed benchmark-ips version

Fixes #29284 - Drop Rackspace support

Refs #29679 - Pin benchmark-ips

Version 2.8.0 is broken and prevents app startup.

Fixes #29676 - explicitly use Rails 6.0 compatible gems

Fixes #29642 - drop sqlite support

Fixes #29673 - Upgrade to Rails 6.0.2.2

Also clean up Rails 5 leftovers in gemfiles and initializers.

Fixes #29670 - upgrade patternfly

Fixes #29522 - upgrade jquery-ui-rails

Fixes #29567 - Add nulldb for build environments

refs #29481 - Pin capybara (#7569)

Fixes #29388 - Add rubocop-minitest

Fixes #29390 - Unpin pry-byebug

Refs #28320 - Allow sass-rails 5.x again

This partially reverts 26dda8dbbf32d357657c3d22018c9d247fb0cb4e. The
reason is that the sassc RPM packaging was broken. However, there's
nothing (yet) that really needs it. This allows testing with the newer
version wil allowing the older one as well.

Refs #28320 - upgrade sass to sassc

Fixes #29163 - Update Rubocop to 0.80

Fixes #29276 - pin statsd-instrument

Fixes #28268 - change v4 to be the default in ovirt cr

Fixes #28823: Pin pry-byebug to less than 3.7.0

Fixes #3678 - Make Pry default development console

Also added a few useful pry plugins that help debugging.

Refs #28217 - Use packaged coffee-rails gem

We currently have 4.2.2 in the rails 5.2 scl, but will need to upgrade
to 5.0 for Rails 6 compat. Using the case statement so we can start
testing Rails 6 before packaging is ready.

Fixes #28217 - drop turbolinks

Fixes #28638 - Require mocha 1.11+

Fixes #28586 - Add application setting to use Rails 6.0

Fixes #28002 - drop Ruby < 2.5

Fixes #28506 - fix upgraded prometheus

Fixes #28121 - Bump fog-ovirt to 1.2.3

Fixes #28406 - pin mocha to < 1.10

Refs #27719 - Specify the fog-vsphere dep clearer

Our gem to RPM dependency converter is not that smart and has a too
verbose output. Before this change:

Requires: %{?scl_prefix}rubygem(fog-vsphere) >= 3.2
Requires: %{?scl_prefix}rubygem(fog-vsphere) < 4.0...

Fixes #28225 - Update Rubocop to 0.75

Fixes #28001 - add rainbow gem to development group

Fixes #28257 - Drop mysql bundler group

Fixes #12063 - require fog-libvirt >= 0.7.0

Refs #28064 - add sidekiq configs

Fixes #28064 - initial script for sidekiq

Fixes #28031 - pin signet on Ruby 2.3

Fixes #27998 - Require minitest-spec-rails 6.x

Fixes #27719 - bumb fog-vsphere

Refs #27666 - Clean up sass-rails pinning

This is semantically the same, but makes it a bit easier on the
packaging side where we have a script that converts it into the RPM
spec. Previously it generated:

Requires: %{?scl_prefix_ror}rubygem(sass-rails) >= 5.0...

Refs #27666 - pin sass-rails on Ruby < 2.4 even lower

Fixes #27666 - pin sass-rails on Ruby < 2.4

Fixes #27313 - Annotation Notes support

Fixes #26782 - Update Rubocop to 0.71.0

Fixes #27068 - Pin spring on Ruby < 2.4

Fixes #27013 - Pin shoulda-matchers on Ruby 2.3

fixes #26918 - add a redis caching backend

Fixes #26906 - update show_me_the_cookies to 5.x

Fixes #26875 - update factory_bot_rails to 5.x

Fixes #26856 - Support for fog-ovirt namespace changes

fixes #26654 - migrate spice to npm and upgrade

• move from an old version of spice to a much newer one (over 5 years upgrade)
• move spice js to webpack
• add alert message if spice fails to initalize

fixes #16287 - Move gridster from bundle to npm

Fixes #26628 - Add service.rb to install puma

Fixes #26607 - Update shoulda-matchers to 4.x

Fixes #26546 - Update Rubocop to 0.64.0