Only pulls recent events on fresh install

Description

The backend will only pull events new than its first ever pull. So new installs will sit there waiting for events to happen, and once one happens, pull all new events after, but never pull any events that happened prior to its first call.

Reproduction

Start up a fresh install following the README, notice no events are populating (give it a few minutes to be sure), go click around in IAM and generate some events. You should now see those generated events, but nothing from earlier.

System information

System:
OS: macOS 15.0.1
CPU: (8) arm64 Apple M1
Memory: 65.67 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.10.0 - /opt/homebrew/bin/node
npm: 10.9.0 - /opt/homebrew/bin/npm
Browsers:
Chrome: 130.0.6723.91
Safari: 18.0.1
npmPackages:
@aws-sdk/client-cloudtrail: ^3.583.0 => 3.670.0
@eslint/js: ^9.11.1 => 9.12.0
@hello-pangea/dnd: ^17.0.0 => 17.0.0
@types/express: ^5.0.0 => 5.0.0
@types/node: ^22.7.5 => 22.7.7
@types/pg: ^8.11.10 => 8.11.10
@types/react: ^18.3.11 => 18.3.11
@types/react-dom: ^18.3.1 => 18.3.1
@types/react-simple-maps: ^3.0.6 => 3.0.6
@types/recharts: ^1.8.29 => 1.8.29
@vitejs/plugin-react: ^4.3.2 => 4.3.2
bcryptjs: ^2.4.3 => 2.4.3
dotenv: ^16.4.5 => 16.4.5
eslint: ^9.11.1 => 9.12.0
eslint-plugin-react: ^7.37.1 => 7.37.1
eslint-plugin-react-hooks: ^5.1.0-rc.0 => 5.1.0-rc-fb9a90fa48-20240614
eslint-plugin-react-refresh: ^0.4.12 => 0.4.12
express: ^4.21.1 => 4.21.1
globals: ^15.9.0 => 15.11.0
nodemon: ^3.1.7 => 3.1.7
pg: ^8.13.0 => 8.13.0
react: ^18.3.1 => 18.3.1
react-dom: ^18.3.1 => 18.3.1
react-router-dom: ^6.26.2 => 6.26.2
react-simple-maps: ^3.0.0 => 3.0.0
recharts: ^2.13.0 => 2.13.0
sass: ^1.80.3 => 1.80.4
ts-node: ^10.9.2 => 10.9.2
typescript: ^5.5.3 => 5.6.3
typescript-eslint: ^8.7.0 => 8.8.1
vite: ^5.4.8 => 5.4.8
vite-express: ^0.19.0 => 0.19.0

Additional information

No response

👨‍👧‍👦 Contributing

• 🙋‍♂️ Yes, I'd love to make a PR to fix this bug!

Start by tracing the backend's AWS CloudTrail event pull during a fresh install, focusing on how the first pull determines the event start point. Reproduce the README setup and compare the initial result with events created afterward. Done means existing events populate on the first pull while newly generated events continue to appear.