zypperpkg: stop logging a spurious ERROR on zypper exit code 104 (nothing found)

[ggiesen]

What does this PR do?

Whitelists zypper's exit code 104 (nothing found) for the search-style calls in the zypperpkg execution module so they no longer emit a spurious ERROR log entry when a search matches nothing.

What issues does this PR fix or reference?

Fixes #58551

Previous Behavior

When pkg.search() (or the internal pattern/patch/version searches) matched nothing, zypper exited with code 104. cmd.run_all's default success_retcodes is [0], so cmdmod._run logged Command '...' failed with return code: 104 even though the search completed normally and correctly reported that nothing was found. The 104 was purely cosmetic log noise; the search itself worked (it uses .noraise and raises CommandExecutionError only via its own empty-solvables check).

New Behavior

The _Zypper wrapper gained an ignore_not_found option that whitelists 104 through cmd.run_all's success_retcodes for the four search-style call sites (search, _get_visible_patterns, _get_patches, and Wildcard._get_available_versions). cmdmod remaps 104 to 0 before its retcode-error log fires, so no ERROR is emitted. The found case (retcode 0) and every genuine error code are left untouched, and a search that matches nothing still raises CommandExecutionError as before.

Note: unlike the earlier closed PR #58552, this change keeps the -x (exact-match) flag on the se -xv call in _get_available_versions; dropping it to se -v is an unrelated semantic change (substring vs exact match) and is out of scope here.

Merge requirements satisfied?

• Docs - n/a (no user-facing interface or behaviour change; log noise only)
• Changelog - changelog/58551.fixed.md
• Tests written/updated

Tests added to tests/unit/modules/test_zypperpkg.py:

• test_search - asserts search() invokes __zypper__(root=None, ignore_not_found=True).
• test_search_not_found_58551 - production-exact reproducer: with cmd.run_all returning retcode 104, search() still raises CommandExecutionError (empty result) and cmd.run_all is called with success_retcodes=[104], proving 104 is whitelisted so no ERROR is logged.
• test_search_without_ignore_not_found_still_errors - inverse guard: a _Zypper call that does not request ignore_not_found must not pass success_retcodes, so genuine non-zero retcodes still surface (passes with and without the fix).

The existing Wildcard tests and ZyppCallMock were updated to match the new self.zypper(ignore_not_found=True) call shape.

Commits signed with GPG?

No