fix: config API bugs, ESP PR #962 custom attributes, scope mismatch fix

[sharmeebuilds]

Summary

• MWPW-196046 (fix 1): Removed ?type= query param from getConfigsForScope — ESP returns 400 on unknown query params; now filters client-side
• MWPW-196046 (fix 2): Added scopeId to createConfig POST body — ESP requires it in the body, not just the URL
• MWPW-196046 (fix 3): Replaced incorrect 409-recovery logic in ConfigManagement.tsx with a proper error toast
• ESP PR #903 cleanup: Removed dead visibleRsvpFields/requiredRsvpFields fields; updated test fixtures to new { fields: [...] } rsvpFormFields shape
• ESP PR #962: Implemented new customAttributes data model — load path flattens grouped API response; save path transforms to IDs-only write shape; added enabledAttributeIds field
• MWPW-195821: Fixed scope mismatch bug where editing an event under a different scope wiped enabledAttributeIds

Test plan

• Config Management: load configs for a scope — no 400 in Network tab
• Config Management: create a custom attributes config — no 400 "missing scopeId"
• Event form: open event with custom attributes, verify values load correctly
• Event form: save event, verify PUT payload has customAttributes as IDs-only and enabledAttributeIds present
• Scope mismatch: create event under Scope A with custom attributes → switch to Scope B → edit any field → save → verify enabledAttributeIds in PUT payload is NOT { "event": [], "session": [] }

🤖 Generated with Claude Code