Blocked by #109791
Part of #105711

Update Since our plan to remove Angular until 7.16 completely I repurpose that issue to remove all Angular code from the i18n framework.

After getting feedback across Kibana, and our plan to eventually move out of angular, ideally we'd want to get rid angular specific i18n code. Namely injecting i18n in controllers/providers/services, i18n filter and i18n directive.

I ran some numbers and we currently have the following i18n count in angular:

• i18n angular directives (HTML i18n-*): 891
• i18n angular filters: 351
• i18n angular providers: 6

Initially for the short term I am thinking we can get rid of angular i18n filters and providers. (356 total locations).

Restricting angular specific i18n to directives. Only allowing i18n in angular html in the following format:

<div
	i18n-id="id"
	i18n-default-message="Default {value}"
	i18n-values="{ value: '<strong>message</strong>' }"
/>

We can get rid of the i18n angular directive (i18n-*) whenever all angular html is converted into react components (long term).

Context #27968

CC @azasypkin