Update the API lifecycle to include deprecated and retired versions #459
Description
Problem description
Today the API lifecycle handle the "sunny day" part of the process, but does not define how to handle deprecated and retired APIs.
Possible evolution
Extend the API lifecycle with information that indicate deprecated and retired state of APIs, and describe how these states are covered in various artefacts, e.g. API table, impact on existing release information in other files, etc.
Additional context
The marketing usage of the API table today is not able to show deprecated and retired APIs.