MINIFICPP-2816 Add controller_service::api_implementations to C api

[martinzink]

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

• Is there a JIRA ticket associated with this PR? Is it referenced
  in the commit message?

• Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

• Has your PR been rebased against the latest commit within the target branch (typically main)?

• Is your initial contribution a single, squashed commit?

For code changes:

• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE file?
• If applicable, have you updated the NOTICE file?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

[Copilot]

Pull request overview

This PR extends the C extension API for MiNiFi C++ to let C-based controller services declare and expose multiple "provided interfaces" (additional C++ APIs they implement). The agent surfaces these as api_implementations in class descriptions, and MinifiProcessContextGetControllerService now uses a new get_interface callback to cast a controller service implementation to a requested API type. A new stable-api-sandbox test extension exercises the feature with Dog/Duck controller services that both implement CanFlyControllerApi and NumberOfLegsControllerApi, consumed by a ZooProcessor.

Changes:

• Added provided_interfaces_* and a get_interface callback to the C controller-service ABI, plumbed through useControllerServiceClassDefinition and useCControllerServiceClassDescription into ClassDescription::api_implementations.
• Introduced a C++-side ProvidedInterface / createProvidedInterface helper and a ControllerServiceType::minifiSystemControllerServiceType factory.
• Added a new stable-api-sandbox extension (controller services, processor, init, tests, CMake) demonstrating and testing the multi-interface controller service flow.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
minifi-api/include/minifi-c/minifi-c.h	Adds provided_interfaces_* fields and get_interface callback to controller-service C ABI structs.
minifi-api/include/minifi-cpp/core/ControllerServiceType.h	Adds minifiSystemControllerServiceType factory and tightens reformatting; private ctor for raw fields.
minifi-api/common/include/minifi-cpp/core/ProvidedControllerServiceInterface.h	New header defining ProvidedInterface and the createProvidedInterface helper template.
extension-framework/cpp-extension-lib/include/api/core/Resource.h	Wires Class::ProvidedInterfaces into the C definition and implements the get_interface lambda.
libminifi/src/minifi-c.cpp	Builds api_implementations from C-side interface names; uses get_interface in MinifiProcessContextGetControllerService.
extensions/stable-api-sandbox/AnimalControllerServiceApis.h	Defines two abstract controller-service APIs used by the sandbox tests.
extensions/stable-api-sandbox/AnimalControllerServices.{h,cpp}	DogController/DuckController implementing both APIs and declaring ProvidedInterfaces.
extensions/stable-api-sandbox/ZooProcessor.{h,cpp}	Test processor that fetches both interfaces from configured controller services.
extensions/stable-api-sandbox/ExtensionInitializer.cpp	Registers the new processor and controller services as a C extension.
extensions/stable-api-sandbox/CMakeLists.txt	New CMake module building the sandbox extension.
extensions/stable-api-sandbox/tests/CMakeLists.txt	Builds the sandbox extension's tests.
extensions/stable-api-sandbox/tests/ZooTests.cpp	End-to-end test exercising multi-interface lookup via the C API.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 14 changed files in this pull request and generated 5 comments.

[martinzink]

Ive renamed it from group_name to module_name, because this groupname was not the groupname in C2 but rather the artifact name

[szaszm]

I like the old version with inline comparisons better. No need to introduce an STL container and ranges when it doesn't have a benefit, and line patterns are easily readable, even if they are somewhat repetitive.

[szaszm]

I just noticed that @lordgamez suggested the change, so CC.

[lordgamez]

It's not really what I suggested, but we discussed that the originally suggested improvement should be a separate PR. Until that is implemented the same issue persists that when any new system allowed type is introduced it needs to be manually inserted here which is not trivial to find and easily missed, does not really matter if it's inlined or extracted to a container. My original intent to alternatively extract the constants was to move them to a more accessible and discoverable place when introducing a new option, but there's not really a viable place for it now, so it can be reverted.

[szaszm]

ah okay. If it's a temporary solution, I don't insist on changing it, but I would still prefer the simpler version.

[martinzink]

yeah since the temp solution wasnt anyones favorite i've reverted that to the simpler version Revert "refactor minifiSystemAllowedType"

[szaszm]

it seems that if filter throws, obj is leaked. Bug not introduced here, and most likely not a problem in practice, since filter functions tend to not throw, I just noticed it.