Add virtural_service/destination_rule to dubbo kubernetes

[YarBor]

What is the purpose of the change

To support future scenario-based configuration to xds mode.

Brief changelog

• Add {virtural_service/destination_rule}.{proto/crds} to dubbo kubernetes,
• format import.
• remove this in generate templete file, it make some bugs in generate vs/ds proto.

{{with $in := .}}
{{range .Selector}}
func (t *{{$in.ResourceName}}) {{.}}() []*{{$pkg}}.Selector {
	return t.Spec.Get{{.}}()
}
{{end}}
{{end}}

• add envoy.cluster.info() call to get cluster match/config info.
• add config set operatoration, mesh-config to xds-protocal in pkg/xds/envoy/virtualhosts/routes_configurer.go
• rename api/mesh/tag.proto.stringMatch to api/mesh/tag.proto.stringMatch_Dubbo, because of name conflict with vs.stringMatch .

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.
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.