alsa-{lib,ucm-conf}: update to 1.2.16.1, alsa-utils: update to 1.2.16

[dogknowsnx]

Testing the changes

• I haven't experienced any sound issues after the update (2 weeks in)
• tested basic functionality of alsactl, alsabat, amixer, aplay and speaker-test

Local build testing

• I built this PR locally for my native architecture, x86_64-glibc

Changes_v1.2.15.3_v1.2.16
Changes_v1.2.16_v1.2.16.1

cc @cinerea0

[biopsin]

I'm hitting on this alsa-project/alsa-lib#510 and will test upstream commit sysfce2/alsa-lib@d983a9c
However I have sound on SSL 2+ Mk2 audiodevice.

[dogknowsnx]

I'm hitting on this alsa-project/alsa-lib#510 and will test upstream commit sysfce2/alsa-lib@d983a9c However I have sound on SSL 2+ Mk2 audiodevice.

As long as it just spams the logs, it doesn't seem 'serious' enough to warrant backporting - let's wait for the next release then? Upstream already released v1.2.16.1

EDIT:

OCI runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH

Will try again later..
..no dice

[biopsin]

Weirdly enough alsa-utils now breaks locally with this error

aconnect.c: In function 'error_handler':
aconnect.c:45:13: error: 'err' undeclared (first use in this function)
   45 |         if (err)
      |             ^~~
aconnect.c:45:13: note: each undeclared identifier is reported only once for each function it appears in

but I see it passes here, meh it packaged yesterday so I will close my blind eye to this..