[refactor](schema_hash) remove schema_hash since every tablet id in be is unique

[caiconghui]

Proposed changes

Issue Number: close #xxx

Problem Summary:

1.Now, schema_hash is part of the data_dir path, but tablet id is unique, so we can read tablet info only by tablet_id,
so this PR only modify get_tablet and drop_tablet function in be, not refactor write schema_hash logic in be.
module in be who use get_tablet and drop_tablet function will be affected.
2. For users, this PR change two httpAction in be, one is metaAction, and the other is CompactionAction. so I also modify the doc and fe code.
3.The main Purpose of this PR is to simplify managing tablet, whether to remove all schema_hash still need more discussion, because we need to consider compatibility and correctness after refactor.

Checklist(Required)

1. Does it affect the original behavior: (Yes)
2. Has unit tests been added: (No)
3. Has document been added or modified: (Yes)
4. Does it need to update dependencies: (No)
5. Are there any changes that cannot be rolled back: (No)

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[yiguolei]

Great.
LGTM

[yangzhg]

1. Does the command line of meta_tool also need to remove schema_hash?
2. Do all the http_action of be has schema_hash should remove schema_hash? If so, you should change the url of fe in show tablet
3. if the above is yes, document is also need to change

[caiconghui]

1. Does the command line of meta_tool also need to remove schema_hash?
2. Do all the http_action of be has schema_hash should remove schema_hash? If so, you should change the url of fe in show tablet
3. if the above is yes, document is also need to change

@yangzhg now, for upgrade compatibility , it is not the time to modify meta_tool, and url of show tablet command,
it just optimize the logic in be to find tablet and drop tablet now

[yangzhg]

1. Does the command line of meta_tool also need to remove schema_hash?
2. Do all the http_action of be has schema_hash should remove schema_hash? If so, you should change the url of fe in show tablet
3. if the above is yes, document is also need to change

@yangzhg now, for upgrade compatibility , it is not the time to modify meta_tool, and url of show tablet command, it just optimize the logic in be to find tablet and drop tablet now

I think it's understandable to bring some compatibility problems when a big version is released, and there are not many users of meta_tool and url, so it's better to modify them together

[caiconghui]

1. Does the command line of meta_tool also need to remove schema_hash?
2. Do all the http_action of be has schema_hash should remove schema_hash? If so, you should change the url of fe in show tablet
3. if the above is yes, document is also need to change

@yangzhg now, for upgrade compatibility , it is not the time to modify meta_tool, and url of show tablet command, it just optimize the logic in be to find tablet and drop tablet now

I think it's understandable to bring some compatibility problems when a big version is released, and there are not many users of meta_tool and url, so it's better to modify them together

I find that I cannot refactor all schema hash code because the schema_hash dir now already in data path,
so in order to be less error prone, I just simplify the get tablet and drop tablet logic in be, and not change interface outside
@yiguolei @yangzhg

[morningman]

Schema hash is currently widely used in various modules of BE and is strongly related to the data itself.
Strict review is required for schema hash modifications.

It is recommended to add the following content to the PR:

1. Which modules currently use the schema hash, and whether it will affect it after removing it.
2. Which modules are modified by this PR
3. Which modules have not been modified
4. What is the next step.

[yiguolei]

Schema hash is currently widely used in various modules of BE and is strongly related to the data itself. Strict review is required for schema hash modifications.

It is recommended to add the following content to the PR:

1. Which modules currently use the schema hash, and whether it will affect it after removing it.
2. Which modules are modified by this PR
3. Which modules have not been modified
4. What is the next step.

This PR mainly modify following modules:

1. It removes schema hash from tablet manager's get_tablet method, and modified the related usage.
2. It removes schema hash from http service's api. [this may cause some usage problems but I think it is ok]

[yiguolei]

LGTM
I've pull the pr to local and build successfully.

[github-actions]

PR approved by anyone and no changes requested.

[morningman]

remove schema_hash in parameter