Cardano Updates

transactions are ordered correctly within blocks (0, 1, 2, ...) and in search results.

Changes:
- Added txIndex field to TxnEntity JPA entity
- Updated JOOQ Transaction and TransactionRecord classes to include TX_INDEX field
- Modified TxRepositoryQueryBuilder to select and map tx_index in queries
- Updated search query ordering to use (slot DESC, tx_index DESC)
- Updated block transaction query to order by tx_index ASC

This ensures:
- Transactions within blocks are returned in correct order (0, 1, 2, ...)
- Search results maintain proper chronological and within-slot ordering
- Consistent pagination for /search/transactions API
- Proper ordering for /block and /block/transaction endpoints

invariants

Fixed 4 failing /construction/parse golden tests that had duplicate
operations at index 3. Tests expected 5 operations but API correctly
returned 4.

Added operation invariant tests to prevent ordering bugs:
- assert_operations_ordered() - ensures operations sorted by index
- assert_operations_sequential() - ensures indices [0, 1, 2, ...]

Covers /search/transactions, /block, and /block/transaction endpoints.

This would have caught the bug where /construction/parse returns
operations in processing order (inputs → outputs → certs → withdrawals)
instead of sorted by operation_identifier.index.

Remove duplicate dRepVoteDelegation operations from integration test
golden files. These duplicates were appearing due to the certificate
processing logic creating operations twice.

This fix aligns with the TransactionOperationParser refactoring that
properly handles DRep vote delegation certificates.

Added store.cardano.return-tx-body-cbor=true to yaci-indexer configuration
to enable returning transaction body CBOR from yaci-store beta5.

This property is required for proper transaction processing and is enabled in:
- Main application.properties
- Test integration properties