Fix the bug of RmiProtocolTest#testRemoteApplicationName

- [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.
- [ ] I have checked the [FAQ](https://github.com/apache/dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.

### Environment

* Dubbo version: dubbo3.0
* Operating System version: macos
* Java version: 1.8

In dubbo3, the ConsumerContextFilter is modified to implement the ClusterFilter interface. When writing test cases, if user directly export and refer the service based on the protocol, the filter will not be loaded, causing the REMOTE_APPLICATION_KEY parameter to not be passed to the provider side.

Movitation:

add a consumer-side filter to pass REMOTE_APPLICATION_KEY to the provider-side

Start with RmiProtocolTest#testRemoteApplicationName and inspect how ConsumerContextFilter is loaded when the service is exported and referred directly through the protocol. Run that test on Dubbo 3.0 with Java 8; done means the consumer-side filter passes REMOTE_APPLICATION_KEY to the provider and the test succeeds.

Written by the indexing model from the issue text.