FINERACT-2595: Fix Liquibase changeset 0231 FK violation on existing tenants

[AshharAhmadKhan]

Problem

Changeset 0231 (merged in #5764) failed on existing tenants with a
PostgreSQL foreign key violation:

DELETE FROM m_permission WHERE code='INACTIVATE_CLIENTCHARGE'
→ ERROR: violates foreign key constraint "fk8dedb048103b544b"
on table "m_role_permission"

This happened because m_role_permission holds references to m_permission
via a foreign key. You cannot delete a permission row while role-permission
rows still point to it.

Additionally, the changeset author was set to "ashharahmadkhan" instead
of the required "fineract".

Fix

1. Delete orphaned m_role_permission rows first, before deleting the
   parent m_permission rows.
2. Change changeset author from "ashharahmadkhan" to "fineract".

Fresh tenants (barebones_db / load_sample_data) were unaffected because
those permissions were never assigned to any role. Existing tenants with
roles assigned to INACTIVATE_CLIENTCHARGE hit the FK violation on startup.

References

• JIRA: https://issues.apache.org/jira/browse/FINERACT-2595
• Original PR: FINERACT-2587: Remove CLIENTCHARGE|INACTIVATE write path (never implemented since 2015) #5764

[AshharAhmadKhan]

Hi @IOhacker, this should fix both issues you reported. Please have a look at this when you get a chance.

[IOhacker]

@AshharAhmadKhan thank you!, looks ok, let's wait for the completition of the GAs .

[IOhacker]

LGTM