UX for super admin to request changes

[emilyjablonski]

The following changes will only affect the partner's portal experience of a super administrator and not a partner.

• Update the seed to include a listing or two that is pending review
• After clicking edit, a super administrator should see the request changes button reflected in the Figma below
• If clicked, it should opens a modal requiring them to enter text into the requested changes section. Only after entering text will submission be possible
• On submit, the status on the listing should change to Changes Requested status (reflected in the pill), the changes requested should be stored on the listing, a success toast should be thrown, and we should see the changes requested in the listing detail form.
• A change request can not be retracted; a super admin will have to either a) wait for a partner to re-request approval to request a new change b) publish the listing if request is no longer relevant

Note: These changes should result in only updating the status of the listing on modal submit. Further functionality such as saving the changes requested and request date to the database will be implemented in later tickets.

Figma

[emilyjablonski]

High character limit When the field is on the listing detail page, it should truncate with show/hide

On a second re-request of changes, the text field prepopulates w the requested changes field

Keep the requested changes field on a listing, but don't show it in the open/closed states

[sarahlazarich]

closing, moved over