[Bug]: when include and exclude configurations are invalid, we don't catch it.

## Invalid configuration should not `validate`.

Today this starts, passes validate and also hot reloads successfully when it should fail.

```json
"permissions": [
{
"role": "anonymous",
"actions": [
{
"action": "*",
"fields": {
"include": ["Id"],
"exclude": ["Id"]
}
}
]
}
],
```

I am also not sure this error message helps the developer debug the situation. And it should.

```json
{
"error": {
"code": "AuthorizationCheckFailed",
"message": "Authorization Failure: Access Not Allowed.",
"status": 403
}
}
```

This implies we are asking for a field that is not available, but we are actually just asking for the entity. It's confusing.

Can we append to the error message? `include and exclude field configuration is invalid.`

Empieza reproduciendo la configuración de permisos JSON con el mismo campo tanto en include como en exclude y, a continuación, sigue las rutas de validación y hot-reload que la aceptan. Compara la respuesta AuthorizationCheckFailed resultante con el error de configuración más claro solicitado; se considera terminado cuando las configuraciones no válidas fallan la validación y el mensaje identifica el conflicto entre include y exclude.

Escrito por el modelo de indexación a partir del texto del issue.