Workaround for directly loading Gem::Version

[hsbt]

What was the end-user or developer problem that led to this PR?

If we use rubygems/version directlry without rubygems, we faced uninitialized constant Gem (NameError) error.

What is your fix for the problem, implemented in this PR?

Pick ruby/ruby@e410d93

Make sure the following tasks are checked

• Describe the problem / feature
• Write tests for features and bug fixes
• Write code to solve the problem
• Make sure you follow the current code style and write meaningful commit messages without tags

[Copilot]

Pull request overview

This PR addresses an issue where directly loading rubygems/version without loading rubygems first results in an "uninitialized constant Gem (NameError)" error. The fix adds a workaround by ensuring the Gem module is defined before the Gem::Version class is declared.

Changes:

• Added a module definition for Gem to prevent NameError when loading the version file directly

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Defining an empty module without checking if it already exists could override an existing Gem module definition. Consider using module Gem unless defined?(Gem); end or checking defined?(Gem) before defining to avoid potential issues.

Suggested change

	module Gem; end
	module Gem unless defined?(Gem); end

[Copilot]

The comment 'in some cases' is vague. Consider being more specific about when this workaround is needed, such as 'when requiring rubygems/version directly without requiring rubygems first'.

Suggested change

	# Workaround for directly loading Gem::Version in some cases
	# Workaround for directly loading Gem::Version when requiring rubygems/version
	# directly without requiring rubygems first