feat: fields and methods to set event type (wildfire or something else)

[blenzi]

This PR adds the possibility to set an event type, different than wildfire. This event assessment is currently done via pyro-platform but this information is only stored locally (in the machine running it).

• add options to EventType enum: domestic fire, chimney, cloud, other, undefined (default)
• add type_set_by and type_set_ts to events table
• add PUT /events/{event_id}/type endpoint and set_event_type method to client

[codecov]

Codecov Report

Merging #291 (3abe13c) into main (5f735c3) will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #291      +/-   ##
==========================================
+ Coverage   95.35%   95.43%   +0.07%     
==========================================
  Files          66       66              
  Lines        1571     1598      +27     
==========================================
+ Hits         1498     1525      +27     
  Misses         73       73              

Flag	Coverage Δ
client	100.00% <100.00%> (ø)
unittests	95.20% <100.00%> (+0.08%)	⬆️

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

Files	Coverage Δ
client/pyroclient/client.py	100.00% <100.00%> (ø)
src/app/api/endpoints/events.py	100.00% <100.00%> (ø)
src/app/models/event.py	96.55% <100.00%> (+1.31%)	⬆️
src/app/models/user.py	93.75% <100.00%> (+0.41%)	⬆️
src/app/schemas/events.py	100.00% <100.00%> (ø)

[frgfm]

Thanks for the PR!
I'm aligned with everything apart from the "set_by" and "set_ts". I think we're mixing the role of APM (being able to access logs / interactions) vs. what needs to be recorded in the DB. My suggestion:

• simply removing the set columns
• I can come up with a PR to add a cool APM I've been using (posthog) where we can explore events like those

Here is a screenshot once it's set: