feat: OpenAPI integration

[NexVeridian]

related #855

cargo check -F openapi
cargo nextest run --test-threads 1 -F openapi

TODO:

• [x] config.yaml
  • maybe no enable: true since that's handled by the feature

    openapi:
    redoc:
    !Redoc
      url: /redoc
      spec_json_url: /redoc/openapi.json
      spec_yaml_url: /redoc/openapi.yaml
    scalar:
    !Scalar
      url: /scalar
      spec_json_url: /scalar/openapi.json
      spec_yaml_url: /scalar/openapi.yaml
    swagger:
    !Swagger
      url: /swagger-ui
      spec_json_url: /api-docs/openapi.json
      spec_yaml_url: /api-docs/openapi.yaml

  • [x] finish .merge(Redoc::with_url("/redoc", api.clone()))
  • [x] openapi.josn and openapi.yaml endpoints for all types
• [ ] split feature openapi into feature swagger-ui redoc scalar
• [x] SecurityAddon
  • put impl Modify for SecurityAddon somewhere, maybe with config
  • set the jwt token location
• [x] tests
  • [x] update src/tests_cfg/db.rs:86:1
  • [x] src/tests_cfg/config.rs
  • [x] config from file test_from_folder_openapi()
  • [x] snapshots
• [ ] docs
• [ ] codegen/document adding #[derive[utoipa::ToSchema)] if used in utoipa::path
• [ ] maybe auto fill / wrap utoipa::path if possible
• [ ] check that get in get(get_action_openapi) is still grabbed with routes!(get_action_openapi)
• [x] fix AppContext - check that api_router.routes(method.with_state::<AppContext>(())) doesn't break the ctx with .layer

cc @DenuxPlays

[DenuxPlays]

Looks like a good start.

I think the yaml also should contain a few other things:

• openapi and ui endpoints (I am not sure if this is want you mean in your description)
• whether it serves json, yaml or both (Perhaps this can be controlled by using features to exclude unnecessary dependencies)