Remove canonical_segments check

[dduugg]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

Ruby 3.1 ships with rubygems 3.3.3, which was released 2021-12-24. Gem::Version#canonical_segments was introduced in 2016.

[Bo98]

This script is used on arbitrary Rubies in the PATH etc to check if it is Ruby 3.1 or later. Though if it still errors out with a non-zero exit code and prints nothing to stdout (stderr is fine since we do 2>/dev/null) on very old Rubies then it's probably ok to remove the check.

[dduugg]

Yeah, tbc I mean that primarily as a contrast. Even macos system ruby ships with rubygems 3.0.3, released in 2019. But reasonable enough if folks want to maintain support for the oldest rubies.

[MikeMcQuaid]

Giving that it will fail as @Bo98 says: makes sense, thanks @dduugg!