chore: use main IDs transaction_id and staging_entry_id for URL routing and data fetching

[susrithasabbini]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This PR updates the ReconEngine URLs and data fetching logic to use main IDs (transaction_id and staging_entry_id) instead of unique IDs. Due to versioning requirements, the application now routes and fetches data using the main identifiers, which allows proper handling of versioned entries.

Key Changes:

• URLs for transactions now use transaction_id instead of unique id
• URLs for transformed entries now use staging_entry_id instead of unique id
• Details pages refactored to fetch directly by main ID and sort by version
• Toast notification links updated to use main IDs
• Table entity getShowLink updated for proper navigation
• Removed unnecessary intermediate API calls in details pages
• Enhanced transaction details field display logic for different reconciliation types
• Improved UI with EllipsisText for Reason field

Motivation and Context

With versioning support in the ReconEngine, each transaction and transformed entry can have multiple versions. Using the unique id field causes issues when navigating and fetching data because it points to a specific version rather than the main entity. By
switching to transaction_id and staging_entry_id (the main identifiers), we can:

• Fetch all versions of an entity and display the latest
• Maintain consistent URL structure across versions
• Simplify the data fetching logic
• Provide better user navigation experience

Fixes: #3846

How did you test it?

Locally

Where to test it?

• INTEG
• SANDBOX
• PROD

Checklist

• I ran npm run re:build
• I reviewed submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with