Fix Net::Ping::VERSION

[taketo1113]

This Pull Request fixes Net::Ping::VERSION.

The version in the net-ping gem's gemspec is 2.0.8, but Net::Ping::VERSION is set to 1.7.6.
To resolve this inconsistency, Net::Ping::VERSION has been moved to a separate file, and the gemspec now references Net::Ping::VERSION from that file.

Steps to reproduce

• ruby: 3.4.1
• net-ping: 2.0.8

require 'net/ping'
Net::Ping::VERSION

Expected behavior

Net::Ping::VERSION
=> 2.0.8

Actual behavior

Net::Ping::VERSION
=> 1.7.6

[eitoball]

Sorry for the delayed review.

[P1] Load Net::Ping::VERSION at runtime — lib/net/ping/version.rb:4
Although it is loaded from net-ping.gemspec, version.rb is not required through the usual require 'net/ping' or require 'net/ping/tcp' paths. As a result, Net::Ping::VERSION raises a NameError, and the version test updated in test/test_net_ping.rb also fails. To preserve the public API, require ping/version from the base class or each public entry point.

[taketo1113]

@eitoball I rebased the branch and added require 'ping/version' to lib/net/ping.rb.

[eitoball]

Thanks for the change! I left two comments — could you take a look?"

[eitoball]

The "README.md" explicitly documents require 'net/ping/tcp'-style individual requires as a way to reduce memory footprint. Under that usage, "version.rb" is never loaded, so Net::Ping gets defined without the constant, and accessing Net::Ping::VERSION raises NameError.

So I suggest to change "lib/net/ping/ping.rb" like:

require_relative 'version'

class Ping
  VERSION = Net::Ping::VERSION

[taketo1113]

I moved it from lib/net/ping.rb to lib/net/ping/ping.rb.

[eitoball]

Thanks! Looks good.
Please rebase and resolve a conflict, so that I can merge this PR.

[taketo1113]

Thank you for reviewing.
I have rebased it!

[eitoball]

LGTM — correct fix for the VERSION drift bug, follows standard Ruby gem versioning conventions, no packaging or behavior concerns.