Core component of SQL Server for storing, processing, and securing data
First of all: This is a technical forum, and your questions are of a legal nature. You cannot get authoritative answers here. We can give advice, but if you go ahead and you are later license-audited, and the license auditor says that you are incorrectly licensed, referring to a forum thread like this one, will carry very little weight. For authoritative answers, you need contact your local Microsoft representative, and make sure that you get answers in writing, so that you have something to show the license auditor.
Next: If you have not read the SQL Server Licensing Guide, do so. I believe that it will answer a few of your questions. Although, this link goes to the guide for SQL 2022, and I believe they did some changes from SQL 2019 to SQL 2022, to the advantage for the customer. But if I understand it correctly, the license you have is for SQL 2022, and in that case, the Licensing Guide will apply, I assume.
Then: From a technical perspective, I would question that you are migrating from a VM to a physical machine and stay on SQL 2019, a version that is out of mainstream support. I would recommend that you upgrade to SQL 2025. But obviously, this comes with a license cost, although this reduced as you have SA.
I will now try to answer your questions, but beware the caveat above. And I did not read the License Guide in detail to check things up.
Can our existing 12-core SQL Server 2019 Enterprise license be reassigned from the production VM to the new 12-core physical server?
I like to believe so. But that is based on common sense (which does not always apply when it comes to licensing!)
If the primary server is covered by active Software Assurance, can the secondary server operate as a passive HA replica without requiring additional SQL Server core licenses?
As long as it is passive, yes. The license guide lists a few things you can do on the passive replica.
If we enable read-only routing and allow Power BI/SSRS developers to execute reporting queries against the secondary replica, will the secondary server require separate SQL Server Enterprise core licensing?
Yes, a readable secondary must be licensed separately.
Can the existing 12-core license be utilized for the primary server while the existing production VM continues hosting the smaller databases? If not, what is the minimum additional licensing requirement for the old VM?
If you transfer the license to the new physical machine, the instance on the VM will be unlicensed, so you will need to get a new license. Now, since these databases are small, you could opt for SQL Server 2025 Express Edition, which is free. Since one of the databases is 10 GB, you will need SQL 2025 where the cap for the database size is 50 GB, as opposed to 10 GB for SQL 2019 and SQL 2022.
Would you need features/capabilities not available in Express Edition for these databases, you will have no choice but to cough up the money for a new license for the VM.
Is there any specific Software Assurance requirement or licensing benefit applicable to our proposed two-node Always On HA configuration with read-only reporting?
No, I don' think so. SA permits you have one more DR copy, but as I recall, and active read-only instance requires full licensing. Again, check the Licensing Guide.
Are there any additional licensing requirements for Power BI Report Server or SSRS when reporting workloads connect to the readable secondary replica?
Again, the readable secondary must be licensed, and if PBIRS/SSRS is running on a separate machine that server must also be licensed.