delete_rpc_rest

[wcy666103]

What is the purpose of the change

take apark of #14061

Brief changelog

Verifying this change

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[finefuture]

Please resolve the conflicts.

[finefuture]

Why were these unit tests removed?

[wcy666103]

They are either using the rest protocol or using the rest protocol-specific userservice definition

[finefuture]

Please remove only the rest-related parts, do not delete the entire unit test class.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[wcy666103]

Is there something wrong with ci? I think recent pr failed on that test @finefuture

[AlbumenJ]

Please follow up #14061. Seperated PR will cause compile issues.