feat: add integration tests

[ifropc]

🤖 AI summary

Key Changes:

• Application Refactoring:
  • Modularized fly-app/src/main.rs by extracting route configuration into a setup_routes function, enabling the application to be initialized in both the production server and the test
    environment.
  • Added fly-app/src/test.rs which provides utility functions for Actix-web integration tests, including test_get for verifying JSON responses from API endpoints.
• Testing Infrastructure & CI:
  • Added a GitHub Actions workflow (.github/workflows/rust.yml) to automate the testing pipeline.
  • Included a docker-compose.yml and a large database dump (fly-app/dump.sql) to provide a consistent PostgreSQL environment for tests.
  • Added helper scripts in fly-app/bin/ for creating database dumps and generating test scenarios.
• Test Data Generation:
  • Introduced a Scenario Generator tool in fly-app/scenarios_generator/ (using Python and Nix/Flakes) that uses scenarios.yaml to define and generate test data/URLs.
• Database Models:
  • Added fly-app/src/generated.rs, a significant addition (800+ lines) likely containing database schema mappings or auto-generated models used by the updated API logic.

This commit effectively transitions the project from unit testing to full integration testing against a live database.

[chadoh]

@willemneal and I researched briefly and Actix gives us a much more idiomatic Rust way of doing code generation using Rust macros, rather than having a separate yaml file which we then parse with python and emit as separate rust files. The yaml→python→rust toolchain feels very over-complicated and brittle to me.

[chadoh]

@willemneal or I will work on a separate PR with a simpler Actix/Rust-based testing setup. It will probably be sufficiently different that basing it on this one is not worthwhile. Closing. (We can continue to reference this work via the closed PR, if we want to borrow anything from this.)