Add create-by audit for scenario creation (again)

[Kanakanajm]

Record user IDs and realm/LHA/Org IDs when creating new scenario. User IDs and Org IDs are extracted from the authentication middleware. I only changed the db model for Scenario but not any DTOs in between (I just changed the signature of those functions in controller and tasks). So far the User IDs are UUIDs generated by Keycloak, not username but we can change that upon request and the Org IDs are just the realm IDs on Keycloak as well. I think we might need to map those onto county code IDs?

Sorry for the weird commit and revert I made on main branch. I accidentally committed there.

[niklasmedinger]

Yes, the LHA/Org IDs need to be mapped to the county codes.

IIRC, Mariama/Jonas mentioned that this mapping already exists. Maybe @JonasGilg can point us to it?

[JonasGilg]

https://github.com/DLR-SC/ESID/blob/develop/assets/lk_germany_reduced_list.json

[NXXR]

Mapping LHA IDs to county codes (or list of nuts) would be useful sooner or later.
Although atm I don't see a reason why we need this immediately 🤔
For access control we would add the LHA/realm IDs to the whitelist anyway no need to go with a mapping detour since access is based on LHAs not country code or similar.
Same when creating scenarios with private LHA data, this would be shared between LHA <-> LHA not for a specific county code, right? ._.

[NXXR]

Hey Jackie,
you need to add the UserId and OrgId to the App's models (at least in /ESID-Backend/api/src/api/app/models/scenario.py) otherwise it will not get returned in the API request but only stored in the DB.
You can still pass it along until the db task and put it in there, since the request only returns the id anyways, or write both into the scenario object as soon as you have the info, both is fine.
Finally, you then also need to fix the scenario_get_by_id task to write the additional ids from the db into the app's Scenario DTO so they get returned properly.

[NXXR]

Since this is the DB model this should probably be a UUID.

Suggested change

	userId: Optional[str] = Field(default=None, nullable=True) # Created by user
	orgId: Optional[str] = Field(default=None, nullable=True) # Created by user's LHA/Organization
	CreatorUserId: Optional[uuid.UUID] = Field(default=None, nullable=True)
	CreatorOrgId: Optional[uuid.UUID] = Field(default=None, nullable=True)

[Kanakanajm]

User IDs from Keycloak are UUIDs but Org IDs are just strings.

[NXXR]

⚠️ Important note for us:
When merging and deploying this we also need to create an alembic migration (see last 2 steps of the setup.md) in order to create the missing columns in the databases. previous entries int he DB will just have null in these fields so it's fine to migrate even with existing data in the database.