Add deduplication for ttl data

[amishas157]

This PR addresses bug reported in #25

This was because a TTL entry can update multiple times within a given ledger entry. We were already deduping contract data entry. This PR adds deduping of ttl entry as well.

Notice keyhash 83c830c6d200adbceda8e72d8204017f781b57e1ec8acf03674388a902732779 in following Example:
Example

                      {
                        "state": {
                          "last_modified_ledger_seq": 896,
                          "data": {
                            "ttl": {
                              "key_hash": "83c830c6d200adbceda8e72d8204017f781b57e1ec8acf03674388a902732779",
                              "live_until_ledger_seq": 1054975
                            }
                          },
                          "ext": "v0"
                        }
                      },
                      {
                        "updated": {
                          "last_modified_ledger_seq": 900,
                          "data": {
                            "ttl": {
                              "key_hash": "83c830c6d200adbceda8e72d8204017f781b57e1ec8acf03674388a902732779",
                              "live_until_ledger_seq": 1054979
                            }
                          },
                          "ext": "v0"
                        }
                      },

[Copilot]

Pull request overview

This PR fixes a bug where multiple TTL (Time To Live) entry updates within a single ledger cause a database constraint violation. The fix adds deduplication logic to remove duplicate TTL entries before database insertion, following the same pattern already established for contract data entries.

Changes:

• Added deduplication for TTL entries using KeyHash and LedgerSequence fields to prevent "ON CONFLICT DO UPDATE command cannot affect row a second time" database errors

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Consider adding a test case in ttl_test.go that verifies the deduplication behavior when multiple changes to the same TTL entry occur within a single ledger. This would help prevent regression of the bug described in issue #25. The test could create multiple ingest.Change entries with the same KeyHash but different values (similar to the example in utils/processor_test.go TestRemoveDuplicatesByFields) and verify that only the latest entry is retained.

[amishas157]

@copilot open a new pull request to apply changes based on this feedback

[Copilot]

@amishas157 I've opened a new pull request, #27, to work on those changes. Once the pull request is ready, I'll request review from you.