Add JRuby 9.3.14.0 and 9.4.6.0

Add mruby-3.3.0

Add Ruby 3.2.3

Skip passing `--with-readline-dir` for Ruby 3.3+

Added 3.4-dev definition

Switch 3.3.0-dev to ruby_3_3 branch

Add Ruby 3.3.0

Use bats-core instead of archived version

Add Ruby 3.3.0-rc1

https://www.ruby-lang.org/en/news/2023/12/11/ruby-3-3-0-rc1-released/

Fix linking to older OpenSSL for Ruby < 2.7.7

Explicitly set PKG_CONFIG_PATH when `--with-openssl-dir` is used for older Rubies.
Otherwise, Ruby will attempt to link to the latest OpenSSL found by pkg-config,
which could be incompatible.

Introduce "with_bundled_gems" build step for dev rubies and unify "standard"

This merges "standard_build" and "standard_install" build steps into one again
and modifies "standard_install_with_bundled_gems" to just invoke "standard"
with the addition of `update-gems` & `extract-gems` targets.

Fix compiling Ruby < 2.5 by omitting `--with-ext`

Using `--with-ext=+` only has the indended effect (compiling all extensions that would normally get compiled) on Ruby 2.5+. On older versions, it causes none of the default extensions to get compiled, resulting in a defunct installation.

Remove deprecated verify_openssl step from build definitions

Instruct Ruby to fail the build if openssl or psych are missing

A very common type of build failure is that the Ruby "openssl" extension failed to compile. However, when that happens, ruby-build just prints a generic "BUILD FAILED" message. To find out what happened, the user would first have to open the ruby-build log, note the "Following extensions are not compiled" section, then figure out how to find the exact location to the "ext/openssl/mkmf.log" file for more information.

Now, when `make` fails, ruby-build will automatically forward the "Following extensions are not compiled" information to stderr.

The functionality to fail the build if openssl or psych are missing is
now built into the `./configure && make` phase for Ruby.

Normally, Ruby `make` step will print a warning about any missing
extensions, but will not abort the build and instead proceed as normal.

Since Ruby installations without openssl or psych are essentially
broken, ruby-build used to have a `verify_openssl` build step to test if
the newly built Ruby can load these extensions, and print helpful
information and abort the build on errors:

    Loading the Ruby openssl extension failed
    ERROR: Ruby install aborted due to missing extensions

The `verify_opensl` implementation was necessary to provide a good
experience for ruby-build users, but was hacky and I would prefer to
eliminate it.

It appears that passing `--with-ext=openssl,psych` to the Ruby configure
step marks those extensions as mandatory and fails the `make` process if
they failed to build. This is exactly the behavior we want, so this
enables the configure option for all Ruby builds.

* Currently the same as 3.3.0-dev but that name changes every year,
  so this makes it easy to install ruby dev/master.

Add script to update `warn_unsuppported`, `warn_eol` labels

Mark Ruby 3.0.x as unsupported