FINERACT-2165: Migrate event, provisioning, and standing instruction helpers to fineract-client-feign

[elnafateh]

Description

• Migrated ExternalEventConfigurationHelper and ExternalEventHelper
• Migrated StandingInstructionsHelper
• Migrated ProvisioningHelper and ProvisioningTransactionHelper
• Updated corresponding integration test suites to use migrated helper classes

Describe the changes made and why they were made. (Ignore if these details are present on the associated Apache Fineract JIRA ticket.)

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Write the commit message as per our guidelines
• Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• Create/update unit or integration tests for verifying the changes made.
• Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[adamsaghy]

Looks half baked cookie...

Please finish the refactor and remove all:

• JSON
• GSON
• Manually creating Lists and Maps

After the refactor we should only use type-safe requests and responses

[elnafateh]

@adamsaghy You're right it looks half done but here's why. the first commit for this PR carries a full migration of these modules

• ExternalEventConfigurationHelper
• ExternalEventHelper
• StandingInstructionsHelper
• ProvisioningHelper
• ProvisioningTransactionHelper

when pushed the migrations then CI failed some DB checks, Indicating some mismatch in the OpenAPI spec from Provisioning* modules (PostProvisioningCriteriaRequestgenerated model serializes the definitions list asprovisioningcriteriavia Jackson, but the server API expectsdefinitions ). Am left w two choice, either drop the Provisioning* modules from the migration or create some workaround/patch, I then choose the former and obviously the revert was not complete

[elnafateh]

what do u think will be best for it?

[adamsaghy]

what do u think will be best for it?

Its fine if backward compatibility check fails due to API or swagger fix

[adamsaghy]

@elnafateh Please review the failing checks.