Applies_to: Allow a “ga&deprecated” special lifecycle status #2631
Description
Context: it looks like the ES team has a frequent case where the add a setting and deprecate it right away;
Today, we need to work around it (for example by succeeding the 2 statuses (ga then deprecated) in 2 different patches (like 9.2.3 and 9.2.4);
The workaround is ok to use but an explicit way to handle this case would be better, as we could more explicitly indicate "Added and deprecated in 9.x" in one go (longer badge and popover but more accurate with the reality of the implementation, which is always preferable)
On Slack @DaveCTurner suggested something interesting:
maybe in future we could have ga&deprecated 9.2.3 as a single thing, that way it can't just be a copy-paste error
More context in this internal slack thread