Draft: Exploring updating dataframe inplace

This branch uses an allpixels dataframe that the allfires objects update inplace. Right now when you do Fire_Forward on this branch the first step is to eagerly load the preprocessed pixels.

I also did some experiments with writing allpixels to disk. It works ok, but it is way faster to rehydrate if you separately save some metadata about the fires: t_st, t_ed.

There are two other fields that would be very handy to save off but they are per-fire/per-t. Those fields are ftype and hull (and potentially fline if you really want to not compute anything later on). Once I realized I needed them I started thinking that maybe I should be thinking about something other than csvs.

Incidentally there is a lot of IO logic around saving data at a particular time and across time, but a lot of it seems to rely on needing to hold multiple allfires objects at the same time.

I like that in this branch the allpixels object is referenced by all the allfires objects but it isn't copied around. This is different from how it works in preprocess where each fire object has its own dataframe.

maap_runtime/Dockerfile

 FROM mas.maap-project.org/root/maap-workspaces/base_images/vanilla:v3.0.1
-ENV MAAP_PGT=PGT-1294-yxgc33hrHOpUCLQxBO7Hh7efXUw2fYjZXpqfTxn50nZe3cGCdD2zRwu0x0zbR-bNTog-8445019b059c
+ARG BUILD_MAPP_PGT_ARG
+ENV MAAP_PGT=$BUILD_MAPP_PGT_ARG
 COPY ./maap_runtime/submit-dps-job.py submit-dps-job.py
-RUN env | grep MAAP_PGT
 # ENTRYPOINT arguments get dynamically passed as part of the `docker run <name> <args>` command
 # example: docker run test hello-world-aimee_ubuntu main aimeeb maap-dps-worker-16gb --params '{"one":"two"}'
 ENTRYPOINT ["python", "submit-dps-job.py"]