Expected API breaking changes for november

[CypherPotato]

Hello!

Since Sisk was built, its API has been reworked several times, with several breaking changes along the way. I'd like to present changes planned for the future, specifically November, and the motivation for each.

• Route parameter and query separation: to start the conversation, I don't even know why I was storing the route parameters in HttpRequest.Query. Starting from the November version, route parameters will no longer be present in the HttpRequest.Query property but rather in the new HttpRequest.RouteParameters.
• Content reading limitation: previously, Sisk would reject any request if the content exceeded 2GB in size, which is the maximum allowed for an array. In this version, the limitation will be 9.22EB. Note that when calling memory read properties like HttpRequest.RawBody or HttpRequest.Body, an OutOfMemory exception will be thrown if the payload is larger than 2GB. This change does not affect HttpServerConfiguration.MaximumContentLength.
• Drop support for .NET 6 and 7: .NET 7 is no longer supported as of May 14, 2024, and .NET 6 will reach the end of its LTS in November 2024. Starting from this update, future versions of Sisk will only support .NET 8 and later.

Furthermore, the new HTTP QUERY method is likely to become a reality in the coming days. If the official RFC is published, Sisk will implement the new method for its router. Also, you could read the Sisk's new blog, where the maintainer publishes tips on using the framework.

Please let me know if you have any objections to these changes and how they might impact your project.

Thank you for using Sisk.