feat: Support encoding uri

[HYOSITIVE]

Related Issue

• string().uri() not working with accented characters #2889

About Changes

• Added optional field encodeUri with default false in UriOptions.
• Added encodeUri in string validation method.
  • Returns encoded URI when both convert and encodeUri flags are true.
• Added a test case to reproduce the issue.

Result

[Marsup]

Looks like you also need to test for convert: false as true is already the default. It's also missing a bit of docs but I can do it if you don't want to. Thanks for your contribution!

[HYOSITIVE]

@Marsup Thanks for the review! I will add a test case for convert: false. Besides that, could you let me know which docs did I miss? I can add those as well.

[Marsup]

Just missing a quick description in

joi/API.md

Lines 3084 to 3089 in 5b96852

	- `options` - optional settings:
	- `scheme` - Specifies one or more acceptable Schemes, should only include the scheme name. Can be an Array or String (strings are automatically escaped for use in a Regular Expression).
	- `allowRelative` - Allow relative URIs. Defaults to `false`.
	- `relativeOnly` - Restrict only relative URIs. Defaults to `false`.
	- `allowQuerySquareBrackets` - Allows unencoded square brackets inside the query string. This is **NOT** RFC 3986 compliant but query strings like `abc[]=123&abc[]=456` are very common these days. Defaults to `false`.
	- `domain` - Validate the domain component using the options specified in [`string.domain()`](#stringdomainoptions).

[HYOSITIVE]

Sorry for the delay. Just updated the PR!

[Marsup]

I'll change it a bit before releasing for some edge cases, but this is good to go, thanks!

[HYOSITIVE]

Thanks, @Marsup! Please close the issue as well. I don't have a permission to do that because I'm not the one who opened it.

[Marsup]

It's published.