Every revision since 4.5.2 follows the support lifecycle of the parent OS (which generally is much more than 3 years)
.NET Framework has never had a license fee. An argument could be made that part of the cost of Windows OS is a .NET Framework licensing fee, but the fact is if you're developing for Framework then Windows is already in your purview.
Admittedly, the .NET Framework is not open source. But a good amount of its source code is available for review:
I wouldn’t bet my career on .Net framework or desktop development in general anymore than Webforms.
The last time I was looking for a job, there were companies that offering me architect positions paying $10K - $15K more than the job I accepted to lead projects that were doing ASP.Net MVC, Sql server, etc hosted on IIS using .Net framework.
I saw the writing on the wall, I took a job that was more or less a vertical salary move, and “self demoted” so I could jump on newer tech.
The new commercial JDK is like Microsoft suddenly asking expensive license fees for using .Net "in production" (which they actually do indirectly, and with clear-cut boundaries, through expensive enterprise Windows SKUs)