Global circuit breaker for all Dubbo RPC services | 如何默认将所有的 Dubbo RPC接口加上全局默认的熔断策略，并且忽略指定的业务异常？

## Issue Description

sentinel集成dubbo，如何默认将所有的rpc接口加上全局默认的熔断策略？并且忽略指定的业务异常？

### Describe what happened (or what feature you want)

### Describe what you expected to happen
dubbo提供者启动后，所有的接口加上一个全局的熔断策略，而不需要去dashboard中一个个配置，目前有100个service我就要配100次，同时，熔断策略中，怎么忽略指定的业务异常，不触发熔断。类似于Hystrix的HystrixBadRequestException。

### How to reproduce it (as minimally and precisely as possible)

1.
2.
3.

### Tell us your environment
spring cloud alibaba 2.2.6
SpringBoot 2.3.2
spring cloud Hoxton.SR9
sentinel 1.8.3

### Anything else we need to know?

No source file, test, or entry point is named. Start by reviewing Sentinel's Dubbo integration and how rules are configured through the Dashboard, then clarify the design for applying one default circuit-breaker policy to every provider interface and excluding selected business exceptions. Done should be demonstrated for both global rule application and exception exclusion.

Written by the indexing model from the issue text.