DNSCrypt Should Be Updated to 2.0.46 To Enable ODOH Support

[ilikenwf]

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

• [x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• [x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• [x] The title contains the plugin to which this issue belongs

Describe the bug

DNSCrypt should be updated to support odoh instead of just anonymous DNS. Additionally, it may be prudent to better document it or update the documentation sometime as it is out of date.

See https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Oblivious-DoH for information on the 2.0.46+ requirement for ODOH.

[fichtner]

It should, but it should also be said someone should do it, which is the initial problem. ;)

[ilikenwf]

Of all the projects I use this one of the few I haven't really put any requests into...

In this particular case, it should be just the version bump and ensuring that the v3 lists are all in the config file...and maybe also the skip_incompatible = true flag set in the appropriate place...

UI wise, I think it's already acceptable, but we should clarify that unless you list explicitly the servers to use, "all" are used. Likewise, relays including odoh will not be used unless you explicitly specify some relays, or the wildcard...which isn't a great idea as they advise you to use relays not hosted by the same group as the servers you're resolving through.