使用@path@post注解时，请求参数中存在Boolean类型时会把Boolean类型识别为Body

bool值isSync、isGray定义在IntentRequestHeaders 实体类中
```
public CompletableFuture executeSkill(
@BeanParam @NotNull IntentRequestHeaders intentRequestHeaders,
@RequestBody @NotNull IntentRequest intentRequest) {}
```
```
@HeaderParam("x-is-sync")
private Boolean isSync;
@HeaderParam("x-is-gray")
private Boolean isGray;
```

报错信息：
_java.lang.IllegalStateException: defined 3 body parameter.
at org.apache.servicecomb.swagger.generator.core.AbstractOperationGenerator.initParameterGenerators(AbstractOperationGenerator.java:222)
at org.apache.servicecomb.swagger.generator.core.AbstractOperationGenerator.scanMethodParameters(AbstractOperationGenerator.java:192)
at org.apache.servicecomb.swagger.generator.core.AbstractOperationGenerator.generate(AbstractOperationGenerator.java:152)
at org.apache.servicecomb.swagger.generator.core.AbstractSwaggerGenerator.scanMethods(AbstractSwaggerGenerator.java:297)_

Start with AbstractOperationGenerator.java, especially initParameterGenerators, scanMethodParameters, and generate, then trace how @BeanParam, @RequestBody, and Boolean @HeaderParam fields are classified for the shown executeSkill method. Reproduce the Swagger generation failure and verify that the two header parameters are not counted as body parameters and no longer produce the defined 3 body parameter exception.

Written by the indexing model from the issue text.