fix(rubygems): Use cascade of endpoints for unknown servers

[zharinov]

Changes

For registries other than rubygems.org, rubygems.pkg.github.com or gitlab.com, following endpoints are queried:

• First request: /api/v1/versions/{package}.json
  • It's useful because it contains date for releaseTimestamp field
  • Optionally, metadata such as homepageUrl will be queried via /api/v1/gems/{package}.json
• Fallback 1: /info/{package} endpoint (example)
• Fallback 2: /api/v1/dependencies (obsolete but still working)

Context

• Closes Support Nexus repository manager for RubyGems #15459

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[zharinov]

• Blocked by refactor(rubygems): Use Result class #23522

[zharinov]

Sorry, made changes at the last moment. PR description is updated accordingly.

[renovate-release]

🎉 This PR is included in version 36.23.1 🎉

The release is available on:

• GitHub release
• 36.23.1

Your semantic-release bot 📦🚀