Silence parser warning and patch version mismatch when loading parser/current

[navidemad]

Description

This pull request adds a factory class RubyParserFactory to temporarily disable verbose mode when loading the "parser/current" library. The purpose is to suppress compatibility warnings that are displayed when the library is loaded with a different Ruby version than the one it recognizes.

Example warning for the release of Ruby 3.4.1 :

warning: parser/current is loading parser/ruby34, which recognizes
3.4.0-compliant syntax, but you are running 3.4.1.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.

By disabling verbose mode, these warnings are suppressed to provide a cleaner output and avoid confusion. The verbose mode is restored after the parser instance is created to maintain the original behavior.

References

• Bump Ruby 3.4.1 whitequark/parser#1056
• marcandre/rubocop-ast@7081f7c
• Pin the version of parser/current to whatever Ruby version we're using dependabot/dependabot-core#5461
• Parser issue rubocop/rubocop#9700

Changes

• Added a new module I18n::Tasks::Scanners to encapsulate the factory class.
• Implemented the RubyParserFactory class with a create_parser method that temporarily disables verbose mode, loads the "parser/current" library, creates a new parser instance, and restores the verbose mode.
• Added descriptive comments to explain the purpose of the module and provide an example of the warning being suppressed.

Benefits

• Suppresses compatibility warnings when loading the "parser/current" library, providing a cleaner output for users.
• Encapsulates the logic for creating a parser instance within a dedicated factory class, promoting code organization and reusability.
• Maintains the original behavior of the Ruby environment by restoring the verbose mode after the parser instance is created.

Issues

• Silence parser warning and patch version mismatch when loading parser/current #612
• Bump Ruby 3.4.1 whitequark/parser#1056

Please let me know if you have any questions or feedback regarding this pull request.
Thank you for considering this contribution to the gem!

[glebm]

I think a much nicer solution to this would be to send a PR to whitequark/parser adding an argument to Parser::CurrentRuby.new that disables the warning

[navidemad]

I made whitequark/parser#1065 we will see, but yeah you are right fixing it on the parser itself it's better, than hotfixing here.