Provide more context around the features lost during license expiration

[jasontedor]

This relates to #59342. With the additional context that we track around exactly which licensed features are used, leading up to license expiration and at license expiration we can provide users even more context around the licensed features they are losing access to beyond the generic message that we log today (e.g., today we say "Machine Learning APIs are disabled" and in the future we could "Machine Learning APIs are disabled, last used on ${timestamp}". If we sort these by timestamp, it will give users upfront the most relevant information about the consequences of license expiration in what is otherwise a very long message.

[elasticmachine]

Pinging @elastic/es-security (:Security/License)