[INLONG-8403][Manager] Support resource migrate to another tenant

[vernedeng]

Prepare a Pull Request

• Fixes [Feature][Manager] Support resource migrate to different tenant #8403

Motivation

We need a set of interfaces to support resource migrate from/to different tenant.

There are three major resources will be migrated from one tenant to another, Inlong Group, Inlong Consume and DataNode.

All migration should be start with a specific Inlong Group , then migrate the group-related Inlong Consume and DataNode.

The migration is followed by these steps:

1. Check if the target tenant exists
2. List all Inlong Stream of this group
3. List all InlongConsume of this group
4. List all DataNode of related StreamSink
5. List all DataNode of related StreamSource
6. Copy DataNode if the the target tenant doesn't have it
7. Change the datanode name of each sink to the new one
8. Copy TenantClusterTag if the the target tenant doesn't have it

Modifications

Describe the modifications you've done.

Verifying this change

(Please pick either of the following options)

• This change is a trivial rework/code cleanup without any test coverage.

• This change is already covered by existing tests, such as:
  (please describe tests)

• This change added tests and can be verified as follows:

  (example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

[fuweng11]

Please add some logs during the migration process.