Adds keyword arguments to configure - Ruby 3.0 support

[toreym]

Background

In ruby 2.7 calling a method like configure(*@arguments) would allow for keyword arguments in a method definition like def configure(my_param:) In Ruby 3.0, positional arguments and keyword arguments have been separated. So they must be accounted for individually

Overview of change

This PR will allow for a configure that accepts positional and keyword arguments as recommended in ruby 3. It will also account for any workflows in redis that were created with a prior version allowing for a drop-in replacement.

Potential breaking changes

• If your workflow configure methods do not have keyword arguments then there is no impact to you. For example, unless you have a workflow with def configure(my_param:) there should be no problem using this version
• Any workflows that are already in redis which previously had keyword args before running this version will be in the array of positional arguments in redis. This PR accounts for that by pulling any hashes from the end of the array and considers them to be a positional argument. Tests were written to account for this, however they may be edge cases in use that could still be an issue.
• Ruby 2.7 or greater is required (keyword args are not supported as they are in 2.7 and 3.0). It may be possible to add ruby 2.6 or earlier support, however it is EOL and the effort may not be worth it.

[matiasmasca]

@mlen @krzyzak @keqi @ferusinfo did you consider adding this PR? What will you do about this issue?

[pokonski]

This is now released under v4.0.0 using a different approach https://github.com/chaps-io/gush/pull/113/files

@matiasmasca @toreym