Add USS & HD Event/Report Models and create cron script to move them to Site model

[derrickmehaffy]

• Create USS Event Model (Merged with Report Model)
• Create USS Report Model
• Create HD Event Model (Merged with Report Model)
• Create HD Report Model
• Build cron script(s) to migrate data from USS/HD to Site Model
• Test using EDMC plugin

As outlined on Discord:

So for example lets take the USS & HD Sites:

Each have 2 "Report" Models:

USSEvent // USSReport
HDEvent // HDReport

The events are completely automated from journal data, almost Zero user input if any. The reports will be for manual user input and can be tied to the event using a oneToOne relationship. Now talking technical, if we go this route the EDMC plugin will need to "POST" the event first, grab the ID then "POST" the report including the eventID in that request.

Then your script comes into play. This, like the body update script, is going to be fairly complex with a few lookups. I haven't yet even discussed this with @[R&D - Web Dev] AdmlAdama but basically the flow goes something like this:

1. Check if system exists, if not, create it & grab systemID (Our internal, not EDSM)

2. (If applicable) Check if body exists, if not create it and attach it to the system. It already exists grab the bodyID

3. (If applicable) Same as body but for ring (We don't have any use for it right now, could change with the mining crap)

4. Check if location exists, if both system & body do this is almost a given, if not create it using the following:
   systemID
   bodyID
   Site Short code (BT, GR, GS, ect)

5. Check if site exists (Is this an update?) if not then create it and attach it to the location using lookups if needed for type of site (GR Alpha, Beta, Gamma, ect)

6. (Currently only applies to the GR/GS) Lookup/Create sub models such as active obelisks and groups ect.

[derrickmehaffy]

Marking as closed for now as USS have been removed and need to rethink NHSS/HD reporting and validation via CAPIv2-Updater