#7127 | Uri: inconsistent query param names (url-encode) when .renderString-ing

[tothpeti]

This PR contains the fix for #7127

• Add encode method in Query object
• Encode query in Uri's fromString method
• Add new test case
• Refactored other ones to match the RFC 3986 requirements

[tothpeti]

Currently I feel like I am a bit stuck with this issue. At the current version of http4s, there are multiple ways of creating URI and add/update Query parameters.
Firstly, when we create a Uri via the Uri case class (or via any of the helper methods of Uri class), the given query parameters aren't encoded at all. However, when we would like to modify the query parameters by using any of the QueryOps methods, the query parameters will be instantly encoded. In my opinion, this inconsistency should be solved as well, because I am pretty sure that this inconsistency will come up again in the future.
My question is: Should I try to do a large refactor to solve the previously mentioned inconsistency? @armanbilge @danicheg