Fix #25721: add the Date branch to the ruby-nextgen Polymorphism runtime
Fixes #25721
AbstractRubyCodegen maps format: date to Ruby Date, but the generated Polymorphism runtime only dispatched Time: cast_raw had no Date candidate (an anyOf/oneOf Date arm always fell through to cast_model → NO_MATCH) and coerce left format: date properties as raw String in from_hash — both symptoms from the issue reproduce on master.
cast_raw/coerce gain Date branches with cast_date/coerce_date helpers mirroring the existing Time semantics (NO_MATCH on parse failure; coerce falls back to raw data), and the generated gems now require 'date' next to require 'time'.
Committed ruby-nextgen samples regenerated via the stock configs (+75 lines across the two runtimes and gem entry files — sample drift otherwise clean). Pre-fix probe reproduced both symptoms; post-fix: format: date → Date in from_hash, DateOrCode.build('2026-05-06') → Date, unparseable strings still raise/fall back per coerce semantics. Sample suites: petstore 23/23, qdrant 813/813 rspec examples.
Summary by cubic
Fixes #25721 by adding Date handling to the ruby-nextgen Polymorphism runtime. format: date values were previously left as raw String by from_hash, and Date candidates in anyOf/oneOf never matched; now cast_raw and coerce dispatch to new cast_date/coerce_date helpers that parse with Date.parse and mirror the existing Time semantics (NO_MATCH on parse failure, raw value fallback in coerce). Generated gems now require 'date', and the petstore and qdrant samples have been regenerated.