Support Ruby 3.2.x - small bug fixes

[linucs]

No description provided.

[elohanlon]

Hi @linucs. Thanks for opening this PR!

I had some recent in-progress changes that I merged today (and released as gem version 1.1.0), and I'm hoping that they'll cover your Ruby 3.2.x needs, and address the couple of casting bugs you found. Could you please check out the new version when you have a chance and let me know?

I also saw that you added converters: %i[numeric date] in your PR, in the CSV.foreach method call in JsonCsv::CsvToJson.csv_file_to_hierarchical_json_hash, but I think that could be a breaking change for current users of this gem, and also doesn't feel like a good fit here for a couple of reasons:

1. This gem is meant for converting between CSV and JSON structures, and JSON doesn't have a Date type. It's completely fine for a user of this gem to convert date strings to Ruby Date objects after a CSV row has already been converted to a JSON hash, but I wouldn't want to do it as part of that CSV-to-JSON conversion step in the gem.
2. I believe the numeric part can already be handled by a field_casting_rules parameter entry (but please let me know if I'm overlooking anything here).

[elohanlon]

2. I believe the numeric part can already be handled by a field_casting_rules parameter entry (but please let me know if I'm overlooking anything here).

One other note about converters: There are certain scenarios where a CSV cell may hold a numeric string value, but a user doesn't necessarily want that numeric string value to be parsed as a number. I have some cases like that in another app that uses json_csv. That's where the field_casting_rules parameter comes in -- to support a user's preference on a field by field basis.