Just from the issue you linked, this commit appears to fix the issue on Arch according to one user. Just have to wait for the Arch maintainer(s) to update the pipewire package on Arch and you should be all set. I wouldn’t flag the package out of date since it’s not a new release yet, but you could file a bug report here: https://archlinux.org/packages/extra/x86_64/pipewire/ to let the maintainers know they may need to cherry pick commits, or just downgrade pipewire and wait a couple days (maybe a week?) until a new release of pipewire is pushed out. Just a waiting game now really.
I have personally downgraded for now to resolve the issue.
I created this post mostly as a heads-up to the EOS community (someone will run into the same issue sooner or later) to hopefully save others some time from needlessly investigating the same issue.
I’m not sure if its worth opening a bug report on Arch since the issue is already both reported and fixed (as you pointed) upstream. I’m confident that there will be a release soon enough judging by the past release frequency of pipewire.