Fixes #2630, #2627

Add policies that check:

• renamed_to type is the same:
  • OK: same standard type to same standard type, enum <-> enum of the same type, string enum <-> string, int enum <-> int,
  • Not OK: string <-> int and such, string <-> int enum, string enum <-> int enum
• renamed_to enum member exists on the same enum and is not deprecated

Fixes existing violations, brings back some dropped deprecations - context https://cloud-native.slack.com/archives/C041APFBYQP/p1756196369228549?thread_ts=1756165118.156879&cid=C041APFBYQP

The reason to keep type the same when renaming is the following: the goal is to apply rename and other transformations in the collector (and make schema transformations more real). Rename transformation would literally rename attribute. We could introduce more complex transformations that could change type, etc, but they are not supported yet. So rename deprecation can only be used with pure renames at least for the time being.