Fix: CSV import origin in transaction API responses (Fixes #2)

[theanilpaudel]

Summary

Exposed transaction import provenance fields (importId and importRowNumber) in the API service transaction responses.

While PostgreSQL migration V18__Add_import_identity_to_financial_transaction.sql already added import_id and import_row_number to financial_transaction and the worker populates them during CSV ingestion, these fields were omitted from the API service entity and response DTOs. This change maps these read-only provenance fields in JPA and includes them across all transaction read/write API endpoints (FinancialTransactionResponse).

Changes:

• Added importId (Long) and importRowNumber (Integer) scalar fields to FinancialTransaction entity.
• Updated FinancialTransactionResponse DTO to include nullable importId and importRowNumber.
• Updated FinancialTransactionMapper to map provenance fields from entity to response DTO.
• Updated controller test assertions (MockMvc) and mapper tests to verify importId and importRowNumber

Related issue

Closes #2

Verification

• Automated Tests: Executed unit and integration test suites for the transaction domain module:

  FinancialTransactionControllerTest

[icastanon]

Looks good. Thanks for the contribution. I approved and merged.

[theanilpaudel]

Hi @icastanon.
Looks like an issue with LOCALSTACK_AUTH_TOKEN on github secrets.