Plain language success message when saving banner (w/ content release)

[rachel-kauff]

Follow up to #6175: Trigger content release when banner content type is saved as published or archived

Users would benefit from a plainer-language success message when they save changes to a banner as published or archived. The message should communicate:

• Confirm that the content saved
• Indicate what happens next (content release)
• Provide a next step (check the status)

Currently:

Potentially (pending more understanding)

ACs

• [ ] UX writing recommendations
• [ ] Possibly: a discussion with Swirt about constraints (E.g. can we combine into one message or do save success and content release trigger have to be in separate phrases?

Not in scope, but on the mind:

• Content design and language patterns for success messages across the application
• How this might change/inform UX work around accelerated publishing

[mmiddaugh]

Note that the success message has improved but does not incorporate all of Rachel's suggestions:

(as seen in Staging 1/2/2024)