Dominik Gedon

@raulillo82 This can also be merged at some point to align the branches with 4.3, too. It is not exactly a test suite fix, though. I did rebase the branch...

Rebase done. Once the tests are finished, I will merge the PR.

Closing until the 5.0 release. After that, we can do those refactors.

Please rebase. I recently also did some of your changes, @maximenoel8, due to errors in the 5.0 Beta 1 BV.

A full test suite run with Ruby 2.7 and the default gems were successful and showed only 2 failures in secondary which are considered flaky tests. [ruby27_consoletext.txt](https://github.com/uyuni-project/uyuni/files/10576834/ruby27_consoletext.txt)   However...

This will get reopened/worked on after the 5.0 FCS.

# deprecated Object#=~ - https://bugs.ruby-lang.org/issues/15231 - https://ruby-doc.org/core-3.1.1/Object.html#method-i-3D~ ## Ruby < 2.7.6  ## Ruby >= 2.7.6   The `match?` method provides a more explicit and readable way to perform...

```bash dominik-ctl:~ # ps aux | grep chrome root 20760 0.6 0.9 33648216 18384 pts/1 Sl 16:43 0:05 /usr/bin/chromedriver --port=9515 root 20768 0.7 9.7 34278968 196732 pts/1 S

## Minitest error Fixed with another minitest import in `env.rb`. ```bash dominik-ctl:~/spacewalk/testsuite # rake cucumber:sanity_check /usr/bin/ruby.ruby3.3 -S bundle exec cucumber --profile default -f html -o results/output_20240812095247-sanity_check.html -f json -o results/output_20240812095247-sanity_check.json...

Closed in favor of https://github.com/uyuni-project/uyuni/pull/9181