`dig +noidn` should not complain about lack of IDN support

Summary

dig reports an error if it is built without IDN support, and the +noidnin and/or +noidnout options are used. This means the options are not useful for a script that wants consistent lack of IDN translation regardless of how BIND is built.

BIND version used

9.11 and later

Steps to reproduce

build BIND --without-libidn2
run dig +noidnout

What is the current bug behavior?

dig complains ;; IDN support not enabled

What is the expected correct behavior?

No noise on stderr.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information