Implement Uber Eats Menu API nested modifier group validation to handle items with options-within-options (modifier overrides)

Steps

1. Model the menu item with a top-level modifier_groups array, each entry containing an id, min_permitted, and max_permitted selection constraint
2. For modifier options that themselves have sub-modifiers, include a nested modifier_group_ids array referencing child groups within each option entity
3. Validate that nesting depth does not exceed the platform maximum (typically two levels for most integrations) before submitting
4. POST the full menu payload to the Uber Eats Menu API and capture any validation errors returned in the error_details array of the response
5. If a modifier group exceeds the max_permitted count or has conflicting min/max values, correct and resubmit the affected group only using a PATCH
6. Confirm the nested structure renders correctly in the Uber Eats consumer app by placing a test order that exercises the nested modifier path