EPU agent data to DB via HTTP API and RabbitMQ

[vredchenko]

• extend HTTP API with full CRUD endpoint placeholders
• update DB schema to conform to shape of data found in EPU Agent parsers
• HTTP API endpoints publish updates to MQ
• MQ consumer propagates updates to DB
  • Acquisition
  • Grid
  • GridSquare
    • fix: No handler registered for event type: grid_square.updated
  • Foilhole
  • Micrograph
• instrument EPU Agent to send data to the API
  • generate entity IDs agent-side using uuid and modify DB model to accept these
  • and for gridsquares, foilholes and micrographs (and possibly acquisition and grid, too) - ensure there's no
    conflict between IDs we auto-generate and use as PKs in DB and IDs generated by EPU
  • Entities:
    • Acquisition
    • Grid
    • GridSquare
    • Foilhole
    • Micrograph
• add status and health endpoints to Core HTTP API
• clean up src/smartem_decisions/model/mq_event.py and src/smartem_decisions/workflow.py
• add debug logging level to CLI and change info statements to debug where appropriate
• refactor starting at RateLimitedFilesystemEventHandler.on_any_event and update to align with the new datastore
• add verbosity param to parse CLI

[vredchenko]

test: python -m epu_data_intake watch -vv ../smartem-decisions-test-datasets/bi37708-28-copy