FINERACT-2354: added e2e test for validation of re-aging with various interest handling is forbidden on written-off loan

[ruzeynalov]

Description

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.

[Aman-Mittal]

PostLoansLoanIdTransactionsRequest reAgingRequest = setReAgeingRequestProperties(//
                LoanRequestFactory.defaultReAgingRequest(), //
                table.row(0), //
                table.row(1) //
        );

        CallFailedRuntimeException exception = fail(
                () -> fineractClient.loanTransactions().executeLoanTransaction(loanId, reAgingRequest, Map.of("command", "reAge")));
        assertThat(exception.getStatus()).as(ErrorMessageHelper.dateFailureErrorCodeMsg()).isEqualTo(403);`

this code is being duplicated many times in this test file, is it possible if we can create a helper function so that we can reuse this multiple times for better maintainability?

[MarianaDmytrivBinariks]

good caught, thanks, gonna add such method