The latest round of software updates triggered an error and leads to an inability to update the raspi-firmware package, which is surprising, because obviously this clash was here before, but didn't trigger an error previously:

Code:
┌──(root��kalipi)-[~]
└─# apt -y full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  raspi-firmware
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4.810 kB of archives.
After this operation, 479 kB of additional disk space will be used.
(Reading database ... 986204 files and directories currently installed.)
Preparing to unpack .../raspi-firmware_1.20220331+ds-1_all.deb ...
Unpacking raspi-firmware (1.20220331+ds-1) over (1.20220328+ds-1) ...
dpkg: error processing archive /var/cache/apt/archives/raspi-firmware_1.20220331+ds-1_all.deb (--unpack):
 trying to overwrite '/lib/firmware/brcm/brcmfmac43456-sdio.bin', which is also in package kalipi-re4son-firmware 5.4.83-20211204
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
dpkg-query: package 'raspi-firmware' is not installed
Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
dpkg-query: package 'raspi-firmware' is not installed
Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
dpkg-query: package 'raspi-firmware' is not installed
Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
Errors were encountered while processing:
 /var/cache/apt/archives/raspi-firmware_1.20220331+ds-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Any suggested action? One would think that new firmware wouldn't be supplied if there were no meaningful fixes, yet why the two RasPi specific packages collide even though kalipi-re4son-firmware is the default kernel for RasPi...