Create object history API

[Donnype]

Changes

Adds an API representing XTDB's entity-history. This can be used to infer when objects were first and last seen (CC @Rieven). This would boil down to filtering the transaction history by "doc is not None" (since these are deletes, not PUT's) and filtering on valid_time. Then the valid time of the first transaction is the "first_seen" and the valid time of the last transaction is the "last_seen".

Demo

The API:

Example transaction log json where I added then deleted Network|internet, then added it again:

[
  {
    "txTime": "2023-11-23T08:56:35+00:00",
    "txId": 0,
    "validTime": "2023-11-23T08:56:34+00:00",
    "contentHash": "df4fe77b0026ef481131a1e2a7d69416e1f98f57",
    "doc": {
      "object_type": "Network",
      "Network/primary_key": "Network|internet",
      "Network/name": "internet",
      "xt/id": "Network|internet"
    }
  },
  {
    "txTime": "2023-11-30T14:21:57+00:00",
    "txId": 155,
    "validTime": "2023-11-30T14:21:57+00:00",
    "contentHash": "0000000000000000000000000000000000000000",
    "doc": null
  },
  {
    "txTime": "2023-11-30T14:22:07+00:00",
    "txId": 159,
    "validTime": "2023-11-30T14:22:07+00:00",
    "contentHash": "df4fe77b0026ef481131a1e2a7d69416e1f98f57",
    "doc": {
      "object_type": "Network",
      "Network/primary_key": "Network|internet",
      "Network/name": "internet",
      "xt/id": "Network|internet"
    }
  }
]

---

Code Checklist

• All the commits in this PR are properly PGP-signed and verified;
• This PR only contains functionality relevant to the issue; tickets have been created for newly discovered issues.
• I have written unit tests for the changes or fixes I made.
• For any non-trivial functionality, I have added integration and/or end-to-end tests.
• I have performed a self-review of my code and refactored it to the best of my abilities.

Communication

• I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
• I have made corresponding changes to the documentation, if necessary.

---

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.

---

Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.

[Donnype]

Done @underdarknl

[ammar92]

Looks good 👍 Just a few remarks, should be good to go soon

[Donnype]

Done @ammar92

[stephanie0x00]

Checklist for QA:

• I have checked out this branch, and successfully ran a fresh make reset.
• I confirmed that there are no unintended functional regressions in this branch:
  • I have managed to pass the onboarding flow
  • Objects and Findings are created properly
  • Tasks are created and completed properly
• I confirmed that the PR's advertised feature or hotfix works as intended.

What works:

There appears to be no impact in the UI. Onboarding flow works, adding an extra URL object works and this is also scanned.

What doesn't work:

N/a.

Bug or feature?:

N/a.