The distinction between a program, project, and product managers seems to be mostly dependent on the company you work at.
All the various "PMs" at companies I've worked for have done largely the same jobs that are some mix of managing the project and figuring out new features for the product.
The difference between ongoing operations, a project, a program, and a portfolio are clearly delineated in the Project Management Book of Knowledge, which is usually foundational knowledge for a project manager. If a person tries to practice project management without knowing this stuff, I’d agree with your use of scare quotes.
I believe that is (or at least was) true at Google - although from what I knew of the role, it sounded like it also covered what I would consider project management. (I think I would often consider program mangement to be coordinating/managing across multiple projects as part of a broader program of work, but I don't think that was what Google meant by that title.)
At Apple, the ubiquitous EPMs are Engineering Program Managers. But yep, I think we're just quibbling over terms that aren't standardized across (or even within) companies, but describe roles that are more or less the same.