tc springcloud服务引用zipkin启动报错“Field existingConcurrencyStrategy”

- [ ] I have searched the [issues](https://github.com/codingapi/tx-lcn/issues) of this repository and believe that this is not a duplicate.

### 1. Bug Description
tc springcloud服务引用zipkin启动报错“Field existingConcurrencyStrategy”

### 2. Environment:
- JDK version:1.8
- OS:
- TX-LCN version:5.0.2
- Others:

### 3. Exception Stacktrace
Field existingConcurrencyStrategy in org.springframework.cloud.netflix.hystrix.security.HystrixSecurityAutoConfiguration required a single bean, but 2 were found:
- tracingHystrixConcurrencyStrategy: defined in URL [jar:file:/C:/Users/Administrator/.m2/repository/com/codingapi/txlcn/txlcn-tracing/5.0.2.RELEASE/txlcn-tracing-5.0.2.RELEASE.jar!/com/codingapi/txlcn/tracing/http/TracingHystrixConcurrencyStrategy.class]
- sleuthHystrixConcurrencyStrategy: defined by method 'sleuthHystrixConcurrencyStrategy' in class path resource [org/springframework/cloud/sleuth/instrument/hystrix/SleuthHystrixAutoConfiguration.class]

Action:

Consider marking one of the beans as @Primary, updating the consumer to accept multiple beans, or using @Qualifier to identify the bean that should be consumed

```
Paste your Exception Stacktrace here!
```

### 4. Tour Idea

Reproduisez l'échec au démarrage avec JDK 8, TX-LCN 5.0.2, Spring Cloud et Zipkin. Commencez par examiner txlcn-tracing's TracingHystrixConcurrencyStrategy avec sleuthHystrixConcurrencyStrategy de Spring Cloud Sleuth. C'est terminé lorsque le TC Spring Cloud service démarre sans le existingConcurrencyStrategy bean conflict existant.

Rédigé par le modèle d'indexation à partir du texte de l'issue.