Bump ci-queue to v0.100.0

[mdwn]

Bumps the Ruby gem version to 0.100.0.

Changes since v0.99.0:

• Verify TLS certificates for rediss:// queue URLs by default #434: Verify TLS certificates for rediss:// queue URLs by default (breaking, see below)
• Fix Dependabot bundler jobs failing on gemspec constant lookup #428: Fix Dependabot bundler jobs failing on gemspec constant lookup
• Fix race in OrderReporterTest#test_forking #426: Fix race in OrderReporterTest#test_forking

(#427 only touches the Python package.)

⚠️ Breaking: rediss:// now verifies server certificates

Versions 0.59.0 through 0.99.0 connected to rediss:// URLs with verify_mode: VERIFY_NONE on redis-rb > 5.0.0 (effectively every install since 0.67.0 pinned redis ~> 5.0). The traffic was encrypted, but ci-queue never checked the server's identity. Starting with 0.100.0, the certificate and hostname are verified against the system's trusted CAs.

Who is affected: anyone using a rediss:// queue URL whose Redis certificate doesn't verify, for example because it's self-signed or signed by a private CA (Heroku Redis is one case). redis:// URLs aren't affected, and neither is Redis with a publicly trusted certificate for the right hostname.

What it looks like: workers print Ran 0 tests and exit successfully. Connection errors are swallowed, just as they are for an unreachable Redis. report then fails with Redis::CannotConnectError … certificate verify failed.

How to fix: trust the issuing CA (e.g. SSL_CERT_FILE=/path/to/ca.pem), or accept the risk and set CI_QUEUE_REDIS_SSL_VERIFY=0 (or CI::Queue::Configuration#redis_ssl_verify = false). See "Redis over TLS" in ruby/README.md.