(https://github.com/ruby/rubygems/pull/9095)

* Rescue when deleting a non-existent cached gem file

When a gem was in the cache, but another process deletes it first, this
delete command fails.

To work around this, I'm rescuing from Errno::ENOENT and swalling the
error. The file is gone, and we can move on.

* Apply suggestion from @kou

Co-authored-by: Sutou Kouhei <kou@cozmixng.org>

---------

https://github.com/ruby/rubygems/commit/b30bcbc648

Co-authored-by: Hiroshi SHIBATA <hsbt@ruby-lang.org>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>

Followup to https://github.com/rubygems/rubygems/pull/8436

It fixed showing the template when requiring a non-existant file but
user code can do much more than just trying to require other code.

I encountered this particular case because of load order issues, where a library wasn't able
to properly require itself when loaded before some other library.

https://github.com/rubygems/rubygems/commit/1c910e5afe

https://github.com/rubygems/rubygems/commit/24523a839e

If a gem has an internal error, that should not make `bundle console`
print the bug report template.

https://github.com/rubygems/rubygems/commit/7432a9a084

At this point, `dep.autorequire` is always nil.

https://github.com/rubygems/rubygems/commit/0fb2b0a70a

This local variable is initialized later on in this file.

https://github.com/rubygems/rubygems/commit/5c15dbd210

It's simpler.

https://github.com/rubygems/rubygems/commit/76f1e3bf05

https://github.com/rubygems/rubygems/commit/a5519f4f79

LoadError is not a RuntimeError.

https://github.com/rubygems/rubygems/commit/4c67549722