HLRC XPack protocol clean up

[vladimirdolzhenko]

Relates to XPack HLRC #29827

There are some requests/responses in xpack protocol, while most requests/responses are in client/rest-high-level (proper place)

Move ( + clean up ) HLRC located at xpack protocol to client/rest-high-level

Note: In most cases everything is there, except maybe some tests like RequestConvertersTests and unit tests.

• Watcher API HLRC XPack Protocol clean up: Migration; Graph; Watcher #34639, HLRC XPack Protocol clean up: Migration; Graph; Watcher  #34964
  • put watch
  • delete watch
• Miscellaneous API HLRC XPack Protocol clean up: Licence, Misc #34469
  • xpack info
  • xpack usage
• Graph API HLRC XPack Protocol clean up: Migration; Graph; Watcher #34639, HLRC XPack Protocol clean up: Migration; Graph; Watcher  #34964
  • graph explore
• Licensing API HLRC XPack Protocol clean up: Licence, Misc #34469
  • put license
  • get license
  • delete license
• Drop protocol module HLRC XPack Protocol clean up: Migration; Graph; Watcher #34639, HLRC XPack Protocol clean up: Migration; Graph; Watcher  #34964
• cross XPack HLRC compatibility tests XPack/HLRC request/response compatibility tests #34547 , XPack/HLRC request/response compatibility tests #35129
• migrate other XPack request / responses tests to a new cross XPack HLRC compatibility approach

Clean up assumes don't extend AcknowledgedRequest, readFrom(StreamInput in) / writeTo(StreamOutput out)

[elasticmachine]

Pinging @elastic/es-core-infra

[hub-cap]

I think it would be good to also clean up the existing actions we moved from, for instance, we tended to add some XContent methods to the existing request/response that are not needed, so lets try to also revert the history of the moved code in the x-pack directory to something that was before we started the migration.