[Question] there is dubbo version and group settings in Selector,but it not works

### Question

I see that there is dubbo version and group settings in selector,and when i invoke a dubbo interface, the path matched the selector and rules.I can see the config in the field SelectorData.handle. But this config is not work because it get the real GenericService by path in MataData, and it doesn't make a match between SelectorData's config(version and group) and the dubboService's config.So what the DubboSelector's config's meaning. is it used for match the real dubbo version?

我设置了dubbo插件内selector的group 和version配置项。然后调用了接口，匹配到了选择器和规则。然后这个配置应该是保存在SelectorData的 handle 字段内。然后到具体选择dubboService调用的时候，是通过MataData构造的，提供了具体的GenericService，然后后续是通过path来从缓存中取的。但是这个是通过元数据注册上来的。选择器内配置的group和version和 GenericService的实际group和version是不一致的，但是还是可以调用，并没有两者的匹配校验，所以选择器内的配置是用来匹配实际调用的dubbo接口的group和version的吗？如果不是的话，这个配置是具体用来干什么的？

Start by tracing DubboSelector, SelectorData.handle, MataData, GenericService, and the path-based cache mentioned in the question. Determine how selector group and version values are intended to relate to the registered service, then document the behavior and configuration meaning; the issue is complete when that relationship is clearly explained.

Written by the indexing model from the issue text.