Gin compatibility

[EwenQuim]

See #263 for more details & discussions

Is your feature request related to a problem? Please describe.

Gin is very popular and a lot of projects and companies are tied with Gin. Supporting Fuego controllers in Gin or Gin controllers in Fuego might be a good eventual transition for companies wanting to migrate to the new powerful Go1.22 router + Fuego OpenAPI capabilities

Describe the solution you'd like
I'm still thinking about what would it look like. Is there any Gin <-> net/http adaptor to begin with?

GIN SUPPORT IS DONE ✅

There is still some issues to do but the basics works.

Issue tracker

• BREAKING CHANGE: Remove pointer from ContextNoBody and ContextWithBody, use interface directly in handlers #286
• Mutualise a part of Context between net/http and gin #288
• Moved all non-net/http related code to the new Engine struct #290
• Generic main handler #300
• Generic route registration #304
• Transform and Validate Gin input #311

TODO

• Route middlewares

[dylanhitt]

@EwenQuim I believe we can close this as well.

[EwenQuim]

We still have to support Gin middlewares. I don't know how we'll do that

[EwenQuim]

I mean, we are supporting gin middlewares through gin.Engine.Use, but not the route handlers chain

[EwenQuim]

we can write an other issue, this is symbolic to close this one ;) 🎉