editoast: log stdcm requests

[hamz2a]

Part of #9724

• Create a PostgreSQL table with columns: trace_id, request, response, created and user_id.
• Store the data of LMR requests in this table.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 84.00000% with 12 lines in your changes missing coverage. Please review.

Project coverage is 79.86%. Comparing base (255cf0a) to head (63990f2).
Report is 10 commits behind head on dev.

Files with missing lines	Patch %	Lines
editoast/src/core/stdcm.rs	16.66%	5 Missing ⚠️
editoast/src/views/timetable/stdcm.rs	87.09%	4 Missing ⚠️
editoast/editoast_models/src/tables.rs	93.33%	1 Missing ⚠️
editoast/src/core/conflict_detection.rs	0.00%	1 Missing ⚠️
editoast/src/models/stdcm_log.rs	95.23%	1 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff            @@
##              dev    #9873    +/-   ##
========================================
  Coverage   79.85%   79.86%            
========================================
  Files        1048     1048            
  Lines      105086   105214   +128     
  Branches      756      756            
========================================
+ Hits        83921    84033   +112     
- Misses      21124    21140    +16     
  Partials       41       41            

Flag	Coverage Δ
editoast	73.40% <84.00%> (+<0.01%)	⬆️
front	89.35% <ø> (+0.01%)	⬆️
gateway	2.18% <ø> (ø)
osrdyne	3.28% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	87.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[leovalais]

Cursory review, I'll test later if this isn't merged beforehand.

I know the list of fields has been discussed in the refinement, but I can think of at least two other columns that could prove useful IMO:

• the date time of the request, allowing us to sort requests by recentness
• the user that performed the request

With these we'd be easily able to provide a feature like "replay my most recent request". Wdyt? (ping @ everyone)

[woshilapin]

Were you able to test if the trace_id in the entrypoint of editoast is the same than the one you log? I'm wondering if it just generates a new one or not 🤷

[leovalais]

Thanks for the changes! A few more comments below:

[leovalais]

Just tested. Works great when authenticated, but the log entry isn't created when authorization is disabled. Probably a unique nulls missing somewhere.

To keep the repo history clean, I suggest merging @woshilapin PR into yours instead of cherry-picking, and he should probably be Co-Author as well.

[hamz2a]

Just tested. Works great when authenticated, but the log entry isn't created when authorization is disabled. Probably a unique nulls missing somewhere.

If authentication is disabled, the superuser profile is granted to everyone:

if disable_authorization {
    return Ok(Authentication::Authenticated(Authorizer::new_superuser(
        PgAuthDriver::<BuiltinRole>::new(db_pool),
    )));
}

In the code, we assign user_id = -1:

pub fn new_superuser(storage_driver: S) -> Self {
    Self {
        user: UserInfo {
            identity: "superuser".to_string(),
            name: "Super User".to_string(),
        },
        user_id: -1,
        user_roles: HashSet::from([S::BuiltinRole::superuser()]),
        storage: storage_driver,
    }
}

This leads to an issue when trying to store the log, because it results in a foreign key error.
@leovalais

[woshilapin]

Thanks for integrating #9947 into your PR. I'll close #9947.

[leovalais]

LGTM. Thanks @hamz2a @woshilapin for the changes!