The coupling of validation and list-images-missing obscures image errors

[ghost]

gha-select-dcs's list-validate mode optimizes the list of documents to validate within a repo, so we validate as few times as possible. That optimization is correct for daps validate itself, as the actual XML validation validates all parts of the current MAIN irrespective of the ROOTID.

The optimization is not correct for daps list-images-missing. That target only checks for images needed to build the current document (i.e. within the scope of the current ROOTID). By and large, results will still be correct as long as we're preferring validation with DC-*-all files (which have no ROOTID). Results will not be correct though for l10n dirs in doc-sle for languages where:

1. more than one guide is shipped and
2. no DC-*-all file is included.

As an example, the broken state of SUSE/doc-sle@15f3b214 gives an a-OK result if you run list-images-missing with the wrong DC file:

doc-sle :15f3b2148 > daps -d l10n/sles/de-de/DC-SLES-all list-images-missing 
The following images are missing:
container_support_matrix
scc_eye_icon

doc-sle :15f3b2148 > daps -d l10n/sles/de-de/DC-SLES-deployment list-images-missing 
All images for document "book-deployment" exist.

I am not sure whether it makes sense to broaden the scope of list-images-missing (or validate --validate-images) so it matches the scope of validate itself. (However, --validate-ids does match the scope of validate itself, so I guess there's precedent.)

[ghost]

Fixed in DAPS 3.3, which is out now.