Suppress method-redefined warnings in generated Ruby SDK models

[mridang]

Suppress method-redefined warnings in generated Ruby SDK models

Which Problems Are Solved

• Generated model classes define both attr_accessor :field and a custom def field=(…) setter, leading Ruby to emit noisy
  warning: method redefined; discarding old field= messages.
• These warnings clutter test output and obscure real failures.

How the Problems Are Solved

• Introduce the warning gem and, in lib/zitadel_client.rb, require and configure it:

  require 'warning'
  Warning.ignore(:method_redefined, __dir__)

  This suppresses all :method_redefined warnings for files under our gem directory at runtime.
• Provide an RBS signature for Warning.ignore so our type checker recognizes the new class method.
• Document alternative “warning‑free” patch strategies using Module#prepend and define_method in Mustache templates.

Additional Changes

• Added an RBS (.rbi) entry for Warning.ignore under tapioca/typed/third_party.
• Included a SimpleCov::Formatter::HTMLFormatter prepend‑patch example showing the same pattern.
• Updated template‑patch guidance in documentation to cover both the warning gem approach and native Ruby alternatives.

Additional Context

• Original issue: generated models redundantly define accessors and custom setters, triggering method redefined warnings.
• Ruby bug tracking this warning hook behavior: ruby-lang issue #17055.
• We use Jeremy Evans’s ruby‑warning gem for scoped suppression.
• Closes Improve the models to ensure that fields don't have two setters #18