My system uses pipewire for audio and there is a file /usr/lib64/pipewire-0.3/jack/libjack.so.0.
I created a symlink /usr/lib64/libjack.so.0 (strace revealed that this was one of the places where digikam looked for the file) and now digikam starts without problems.
However I do not know if my “workaround” will not cause any other (yet unknown to me) problems in the future operation of digikam.
# zypper in libjack0
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: the installed pipewire-libjack-0_3-0.3.71-3.1.x86_64 conflicts with 'libjack0' provided by the to be installed libjack0-1.9.22-2.1.x86_64
Solution 1: deinstallation of pipewire-libjack-0_3-0.3.71-3.1.x86_64
Solution 2: do not install libjack0-1.9.22-2.1.x86_64
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
Apparently digikam is not built against libjack but tries to load it at runtime and gets confused by non-standard location.
pipewire-libjack adds ld.so.conf.d snippet to resolve libjack.so.0 to /usr/lib64/pipewire-0.3/jack/libjack.so.0, so effectively it does the same as what you did.
Consider submitting openSUSE bug report against pipewire. May be instead of playing with ld.so.conf they consider using alternatives for libjakc.so.0.
IOW - do not do anything differently from host erlangen. Only the host erlangen has the correct installation of openSUSE. As soon as you do anything differently, you are doing it wrong simply because you do it differently.
In a comment in that bug, I included the URL of this thread, and noted that without pipewire-libjack-0_3, 15.5/KDE3 users who wish to use (actively developed) pipewire to the exclusion of (minimal/maintenance mode) pulseaudio may have no way to enable system sounds.
While existing Tumbleweed systems automatically selected package libjack0 in the past a pristine installation on 2022-06-02 selected package pipewire-libjack-0_3.
Users wanting to use digikam without further hassle may deinstall package pipewire-libjack-0_3 and install libjack0 instead.
Pipewire developers’ style of development is plain and utter PITA, in my opinion of course.