ls: resolve --dired by argument position

[ChihweiLHBird]

Summary

--dired forced long format no matter what followed it. GNU treats -D like -g, -o and -n that a later -C, -x, -m or --format= wins, and dired output is emitted only when the final format is long and no --hyperlink comes after the last -D.

Before this PR, uutils could not see where -D was. clap's overrides_with with --format= and --hyperlink deleted the flag from the matches, and the argv scan added to work around that (is_dired_arg_present) also matched files literally named -D.

Behaviour Comparing to GNU

One file a, stdout a pipe

Command	Before	After (= GNU 9.10)
ls --dired -C a	long listing	a
ls --dired -C --zero a	error, exit 2	a\0
ls --dired --hyperlink=never a	long, no //DIRED//	long + //DIRED//
ls -CD --hyperlink a	columns, hyperlinked	long, hyperlinked
ls -lD --format=vertical -l a	long, no //DIRED//	long + //DIRED//

One file literally named -D, stdout a pipe

Command	Before	After (= GNU 9.10)
ls -- -D	long listing	-D
ls --zero -- -D	long listing, NUL-terminated	-D\0

Files aa and bb, bb accessed more recently, stdout a pipe

Command	Before	After (= GNU 9.10)
ls --dired -C -u aa bb	long + //DIRED//, name order	bb aa (atime order)

One file a b, stdout a terminal

Command	Before	After (= GNU 9.10)
ls --dired 'a b'	a b, --quoting-style=literal	'a b', --quoting-style=shell-escape

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/cut/bounded-memory (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/date/date-locale-hour (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/tail/retry (fails in this run but passes in the 'main' branch)
Skipping an intermittent issue tests/date/resolution (passes in this run but fails in the 'main' branch)