FINERACT-2733: add optional payment details to transfer transactions

[AnvayKharb]

Description

Adds optional Payment Detail support to Account Transfer Transactions while preserving backward compatibility.

Transfer transactions can now reference the existing Fineract Payment Detail model when payment information is provided. Existing transfer requests without payment details continue to work without modification.

Changes

• Added optional PaymentDetail support to account transfer transactions.
• Linked transfer transactions to PaymentDetail through a nullable database relationship.
• Updated the transfer creation flow to persist and associate payment details when supplied.
• Reused the existing Payment Detail infrastructure without introducing duplicate logic.
• Extended transfer responses to include payment details when available.
• Added a forward-only Liquibase migration.
• Added and updated tests covering transfers with and without payment details.

Backward Compatibility

• Payment details remain optional.
• Existing transfer requests continue to work unchanged.
• Existing transfer records remain valid without migration of historical data.

Related Issue

FINERACT-2733

Checklist

• Payment details are optional.
• Existing transfer functionality remains unchanged.
• Backward compatibility is preserved.
• Database migration is forward-only.
• Tests added/updated for the new functionality.
• No unrelated changes included.

[AnvayKharb]

@IOhacker i tried to fix this can you please review again

[IOhacker]

@AnvayKharb please sign the commit

[AnvayKharb]

@IOhacker please review again

[IOhacker]

LGTM

[IOhacker]

LGTM