Upgrade JAXB Runtime to 4.0

Multiple framework and extension components use JAXB for annotating objects and processing XML documents. Java 11 removed JAXB from the JDK, requiring the inclusion of external libraries to use JAXB components. This required providing the JAXB libraries in a separate directory, which NiFi loads when running on Java 11 or higher.

JAXB 3 introduced changes that renamed component packages from javax to jakarta. This change breaks API compatibility with version 2, but implements the same functionality with new package names. Upgrading to the new JAXB 3 and Jakarta API packages would remove the need for separate build and runtime profiles specific to Java 11 or higher.