Audit openssl requiring code

[deivid-rodriguez]

Description:

This PR reviews all code requiring openssl in both repos, and centralizes it as much as possible.

As a result, this PR fixes #3173, and closes #3059.

It also fixes https://bugs.ruby-lang.org/issues/16475.

I added a small test (just run gem list bundler) to make sure that bare functionality of rubygems still works without openssl.

Tasks:

• Describe the problem / feature
• Write tests
• Write code to solve the problem
• Get code review from coworkers / friends

I will abide by the code of conduct.

[hsbt]

This pull-request is useful.

But I'm still not sure why we should support non-openssl environment. Is there real use-case it?

[deivid-rodriguez]

Looking at the issues that came up, very few people, but still some people, have such environments.

I think we could consider fully dropping support for non-openssl environments on the next major version. But the way this got broken was completely unintentional and we still have code around (what I'm unifying here) to actually support non-openssl environments.

So, I think we can restore bare support for these environments for now (note that without this fix, as per the ruby-core issue, ruby won't even install without openssl).

Also, note that fixing this was only a side effect, my original intention was to unify the code that requires openssl to try to figure out the jruby failures we are currently experiencing (like https://github.com/rubygems/rubygems/runs/864749290?check_suite_focus=true). But since I was at it, I decided to fix this.

[deivid-rodriguez]

This PR makes the code dealing with loading openssl more unified and clear, and also fixes some (admittedly rare) usages as a side effect. So I'll merge this after CI passes. We can consider fully dropping all usages without openssl for rubygems 4.