dig doesn't show the values of at least +timeout and +retry in the cmd-field, depending on the order

Summary

dig command field doesn't show the assigned value of at least +timeout=XXX and +retry=XXX, depending in the order of appearing.

BIND version affected

$ dig -v
DiG 9.20.2

Steps to reproduce

Unexpected

Issue the following dig command and make sure, that +timeout=3 and +retry=3 are NOT at the end of the command

$ dig +noall +cmd +timeout=3 +retry=3 isc.org

; <<>> DiG 9.20.2 <<>> +noall +cmd +timeout +retry isc.org
;; global options: +cmd

The reported line ; <<>> DiG 9.20.2 <<>> +noall +cmd +timeout +retry isc.org doesn't show the assigned values (seconds).

Expected

Issue the following dig command and make sure, that +timeout=3 and +retry=3 are at the end of the command

$ dig +noall +cmd isc.org +timeout=3 +retry=3

; <<>> DiG 9.20.2 <<>> +noall +cmd isc.org +timeout=3 +retry=3
;; global options: +cmd

The reported line ; <<>> DiG 9.20.2 <<>> +noall +cmd isc.org +timeout=3 +retry=3 shows the assigned number of seconds.

What is the current bug behavior?

dig doesn't show the assigned values of for example +timeout=xxx or +retry=xxx, depending on the order of the command.

What is the expected correct behavior?

I assume dig should print the cmd-line with the correct values, independent on the order of +timeout or +retry in the issued command.