NIFI-14027 Add SSLContextProvider Controller Service Interface

[exceptionfactory]

Summary

NIFI-14027 Adds the SSLContextProvider Controller Service interface to the nifi-ssl-context-service-api and refactors most existing references from SSLContextService to SSLContextProvider.

The SSLContextProvider interface includes the createContext and createTrustManager methods from SSLContextService along with a new createKeyManager method.

These methods return the common objects necessary for TLS communication, without providing access to the underlying configuration properties. This abstraction decouples TLS communication capabilities from key and certificate files. This approach provides the foundation for subsequent support of PEM Key and Certificate files in a new service implementation, building on framework support implemented in NIFI-14001.

The following extension components retain references to SSLContextService as they require direct access to the Key Store and Trust Store configuration files:

• CaptureCahngeMySQL
• StandardHashiCorpVaultClientService
• ConsumeJMS
• PublishJMS
• Kafka3ConnectionService
• ConsumeMQTT
• PublishMQTT

All other Processors and Controller Services keep existing property names, but reference the SSLContextProvider interface in place of the SSLContextService interface.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using mvn clean install -P contrib-check
  • JDK 21

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[pvillard31]

Code changes LGTM, and I have confirmed proper behaviour with a few flows. Thanks for the changes @exceptionfactory !