Fix Ruby 2.7 warnings (required updating to the latest dry-types version)

[elthariel]

This PR upgrades to the latest dry-types to get rid of the ruby 2.7 keyword argument warning. It also fixes the spec to remove most warning. A few remain that aren't fixed in rspec and recursive open struct

[matti]

@elthariel I invited you to write to the repository. If you still have energy, please merge these.

[matti]

merging anyway, nobody maintains this gem, trying to get this working with 3.x now

[matti]

didn't work, reverted

[dwillett]

Hey @matti - I was looking at changes needed to support 3.0.x as well, wondering what remaining issues you were seeing?

[matti]

dry-types / dry-structs upgrade, the API has changed

…

On 20. Jan 2022, at 0.58, Dave Willett ***@***.***> wrote:  Hey @matti - I was looking at changes needed to support 3.0.x as well, wondering what remaining issues you were seeing? — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.

[dwillett]

More so than what was accounted for in this reverted merge? I made similar changes in my fork here to bring it up to compatibility and my unit tests are passing. Wondering if there are additional errors I'm not seeing: dwillett@c39e7de

edit: made some additional updates to fix the docker-compose for 2.6, 2.7. and 3.0

[matti]

@dwillett the error was that Gemfile.lock is not in version control and therefore I couldn't bundle.

merged your master and released as 0.12.0

also sent you an invite to become a maintainer: https://github.com/k8s-ruby/k8s-ruby/invitations