Maven-Jakarta-webapp generation

### Apache NetBeans version

Apache NetBeans 27

### What happened

when generating the default maven webapp the default app downloads and works as expected.
This is currently defaulting to 11.0.0-M1 (needs to be upgraded to stable)
When the properties/framework - jsf option is selected it now locates (registered 2.3 (finally) ) then it falls over.
The auto-generated web.xml file is populated with references to javax.faces.PROJECT_STAGE and javax.faces.webapp.FacesServlet.
Should default to EE 11.0.0 and javax references changed to jakarta.

### Language / Project Type / NetBeans Component

_No response_

### How to reproduce

create default maven webapp
run app (should work)
navigate to properties dropdown
navigate to frameworks option and select JavaServerFaces
this should select jsf registered library (2.3)
re-run app and it will fail - looking for javax.faces.webapp.FacesServlet
navigate to web.xml file and you will see the javax classes referenced.
Also the javax.faces.facelets are added dependencies in the POM.xml file when they are not required as jakarta classes are in the standard jakartaee-api-11.0.0

### Did this work correctly in an earlier version?

Apache NetBeans 26

### Operating System

Ubuntu 25.04

### JDK

openjdk 21.0.8 2025-07-15

### Apache NetBeans packaging

Apache NetBeans Snap Package

### Anything else

_No response_

### Are you willing to submit a pull request?

No

Reproduce the default Maven webapp, select JavaServerFaces in the Properties > Frameworks option, and inspect the generated web.xml and pom.xml. Compare the generated EE version and JSF references with the reported Jakarta EE 11 behavior; done means the app runs without javax.faces references or unnecessary javax.faces.facelets dependencies.

Written by the indexing model from the issue text.