[Deprecations service] add deprecationType and use it in configs deprecations

[Bamieh]

Summary

Ada a new field deprecationType. The field is used to identify between different deprecation types. Example use case: in Upgrade Assistant, we may want to allow the user to sort by deprecation type or show each type in a separate tab.

Current TS definition of the field:

deprecationType?: 'config' | 'feature';

The deprecationType values are predefined to reduce having similar definitions with different keywords across kibana deprecations. Allowing any string to be used as a deprecationType would reduce the usefulness of this field.

The new field is optional. UA might need to categorize deprecations with no deprecationType specified to an uncategorized grouping.

The field is optional to:

1. not all deprecations fall into a general category of types; we can introduce uncategorized as a dedicated category but that would be almost identical to making the field optional.
2. reduce the amount of change required to introduce this feature.

Changes

1. Add deprecationType to deprecations service external contract DeprecationsDetails.
2. Set deprecationType: 'config' for configs deprecations.

Closes #96060

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[pgayvallet]

Implementation looks fine. A few NITs and comment on the tests

[pgayvallet]

Why is it required?

[Bamieh]

I have a test suite #registerConfigDeprecationsInfo which is a private method

[pgayvallet]

Method method = TargetClass.getDeclaredMethod(methodName, argClasses);
method.setAccessible(true);
method.invoke(targetObject, argObjects);

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: cc93244
• Storybooks Preview

Metrics [docs]

Unknown metric groups

API count

id	before	after	diff
core	2281	2282	+1

References to deprecated APIs

id	before	after	diff
canvas	29	25	-4
crossClusterReplication	8	6	-2
fleet	22	20	-2
globalSearch	4	2	-2
indexManagement	12	7	-5
infra	261	149	-112
lens	67	45	-22
licensing	18	15	-3
lists	239	236	-3
maps	286	208	-78
ml	121	115	-6
monitoring	109	56	-53
securitySolution	390	346	-44
stackAlerts	101	95	-6
total			-342

History

• 💚 Build #128160 succeeded cb36b15
• 💔 Build #128153 failed 41b96a1
• 💔 Build #128144 failed 3f1056d

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.