We first need to know if the wifi adapter is seen and configured.
Please post the output of inxi -Fzx and ip address. rfkill may also assist.
Please use the </> Preformatted text tags when posting data from your screen so it retains the formatting you see and makes it easier to read. I took the liberty of editing your post above so you could see the difference in how it is displayed here.
I watch this forum regularly and so far have not noted anything pointing to 5.19.14. Only specific wifi drivers and cards, and even then nothing showing an abnormal bump in problems encountered.
Regardless of the cause, enough info is needed to do troubleshooting and without info there is no way to identify what is happening. Please consider asking for details instead of pointing a finger at what may or may not be the actual cause.
What about the output of lspci -nn | grep Qualcomm so we can see the actual chipset.
It seems the driver is loaded according to the inxi output, though it would have been appreciated if the full output had been posted so other related details may have been seen.
With the proper driver loaded you should be able to use the network settings panel and configure that interface. The gnome network settings is available either through the activities menu or by the icon in the upper right corner of the screen.
This site Commits · kvalo/ath11k-firmware · GitHub shows updates thru Sept 19, 2022 so it may be necessary to update the driver. I don’t find a board.bin file on my system and do not have that Qualcomm board so cannot test. The error message seems to indicate it should be the same location as the board-2.bin file.
What if you tried linking ln -s /usr/lib/firmware/ath11k/WCN6855/hw2.1/board.bin.xz /usr/lib/firmware/ath11k/WCN6855/hw2.0/board-2.bin.xz. That would avoid renaming and would have the other file name for testing. It may work and should not harm, although it may change the error message. It also might be worth testing in linking board.bin.xz to each of the other files in …/hw2.0/ as well with various iterations if the first try does not work. Specifically amss.bin.xz, m3.bin.xz and regdb.bin.xz, though the latter would be my last guess.
I found that all the files in hw2.1 actually are links to the files in …/hw2.0/ anyway, and that all were last updated with a Sep 29 date. They likely contain all the updates of that firmware from the Sept 19th commit.
I suspect that since the only thing you did with that file was to uncompress it from board-2.bin.xz to board-2.bin your approach may not work. (a shaw256sum shows the uncompressed file and the downloaded file are identical). The system expects to be working with a compressed (.xz) firmware file; which is why all the provided files are xz compressed.
Further investigation shows that the amss.bin.xz file is a 32 bit elf executable for Arm, and the m3.bin.xz file is a 32 bit elf executable for x86. The board-2.bin.xz and regdb.bin.xz files are both binary data.