Sometimes those authors have their hands tied. I work with a cross-platform framework and have recently gotten bug reports on my app that the iPhone 14 has the issue described in the thread. The reports have been solely from iPhone 14 users. After some research, I've seen the issue personally and confirmed that the 14 is the only phone my app is deployed to that has this issue. There is no documentation from Apple that said there were camera API changes between 16.0 and 16.0.2, yet I only started getting the reports after the release of 16.0.2.
I bet most of the 3rd party apps don't access the Apple API directly but rather use cross-platform libraries to make the calls. I can't do anything about my own situation, where nothing has changed in the API that I use (I still access the iPhone camera through the same device ID that I always have, using the same configuration for focusing. There's no new device IDs listed in the system on the 14 that wasn't available on the other iPhones. The same code works on every phone except for the iPhone 14). The developers in this case can't simply "code it better" without re-coding the entire App specifically for iOS in Swift or Obj-C, which isn't feasible for any business. Regardless, Apple has been very good in the past about making their interfaces backwards-compatible with existing code so that Xamarin/Qt/Flutter/etc. can continue working well with no changes even after major updates to iOS. Maybe the Walmart apps for different platforms were written specifically for those platforms, and that's why the Walmart app you mentioned earlier isn't having the same issue.
If an Apple engineer is reading this, perhaps you might take a look into whether it's cross-platform frameworks specifically that have this issue?