feat: Validate swagger definitions

[mtojek]

Fixes: #3522

This PR concludes the autogenerating docs initiative with a basic Swagger validator and custom rules, that will let us keep the better quality of docs. The validator uses go/ast to parse comments and Go structure fields. It covers OSS and Enterprise chi handlers.

Checks:

1. Ensure consistency between @Summary and @ID.
2. Verify @Success and/or @Failure.
3. Verify presence of required annotations.
4. Make sure that Go comment (above the function) is before swagger's @...
5. Ensure that path parameters are defined.
6. Ensure that @Security tag is present.
7. Verify @Accept annotation.
8. Verify @Produce annotation.
9. Ensure unique swagger routes - no copy/paste mistakes.
10. Make sure that uuid.UUID and time.Time fields are formatted.

To reviewer:

• There are many files in this PR, mainly due to minor fixes spotted while implementing the validator. I suggest starting the peer review with coderdtest/swaggerparser.go.

[johnstcn]

I haven't gone through the generated docs with a fine-toothed comb, but I just had a couple of questions/observations about the Swagger parser.

[johnstcn]

This is pretty neat 👍

[Emyrk]

Love how easily the go parser was to get comment groups.

I would suggest we should comment what each assertion does. Some are obvious, but it would be helpful to have some english.

Do you intend to parse the go code at all? Like enforce all routes have a swagger defintion? I missed the Chi walker at first. Neat!

Do you intend to dig into the functions and seeing if the return type is called via httapi.Write? Curious if you think we should do any more analysis on the types, via the SDK or the route functions.