Chuck, I had a very similar problem on my MacBook Air (2020) that somehow migrated to my MBP 2022. I think the problem was on my 2011 MBP initially but cannot remember that far back.
Frustrating. I realized that the culprit managed its way onto the new machine when I moved data from the Air to the Pro via a Carbon Copy Cloner restore.
Since there is really no easy and though way to reformat an SSD so that one knows there is not a thread of anything old left on it, I asked my Apple dealer to do it. It took a lot of convincing that I wanted a better than VIRGIN MBP. They did as I asked. Then, using an external Toshiba T5 SSD, I moved only the data files I needed from the SSD to the MBP.
I then downloaded absolutely fresh copies of the programs I needed from the net. I chose this order so that the freshly downloaded apps were initially opened using that data file I had just placed on the drive. I did NOT want the app to create a new file. (The drag and drop feature works quite well here.O
I copied no files from the ~Library ƒ. I even rebuilt my Little Snitch database from scratch instead of loading my saved prefs file.
The problem was fixed. I cannot promise nor guarantee that my solution would work for you. If you have the time, and a number of faithfully executed backups, It just might be the ticket out of your thicket. If you do take me up, I really would like to know the outcome.
I just want to reiterate that ONLY data files that one must need gets copied to the newly completely erased internal drive that has a pristine Mac operating system installed via the restore option menu. I needed to have religion, patience, and more patience but I did kick my problem to the curb. I sure am hoping that I never have to do that again! 