Feature/ms update

[nick-j-roberts]

• Adds plugin which looks up s3 docs created during SST modeling runs, adds id, category, and tropical storms attributes and modifies metadata to include link to png url for SST output, then outputs final doc in JSON format
  • output can be consumed by meilisearch to add or update documents backing the stormviewer application
• Revises meilisearch upload method

[nick-j-roberts]

Things to consider:

• the methodology I use requires a JSON document containing tropical storm data to be on s3
  • I think this makes sense because @ahdietrich sent me JSON data specific to Trinity watershed and transposition region, so this should not be made a constant or anything like that
• I do not know how dynamic the front-end design of the stormviewer application is, so it is unclear if updating the meilisearch database to have an additional filterable attribute of tropical storms is going to require changes on the front end to utilize this filterable attribute

[nick-j-roberts]

I just changed the tropical storm data for the meilisearch document as having a list of objects associated with each document would make it difficult to use in filters, which is what I would think the purpose of this data is. It is easy to revert to a list of objects, but would need clarification on how this would be interacted with on meilisearch

[nick-j-roberts]

I have renamed the plugin from ms_update to doc_rank to reflect that the utility of the plugin is not solely geared towards meilisearch consumption

[nick-j-roberts]

As a side note, the docs from the Trinity SST runs are missing the watershed name. This causes issues with path name creation in the documents, but I can add an override to pull the watershed name from provided plugin parameters instead of the document to take care of this.

Example of missing data from s3 docs for Trinity (s3://tempest/watersheds/trinity/trinity-transpo-area-v01/72h/docs/19790201.json):

"metadata": {
    ...
    "watershed_name": "",
    ...
  }

[nick-j-roberts]

As a side note, the docs from the Trinity SST runs are missing the watershed name. This causes issues with path name creation in the documents, but I can add an override to pull the watershed name from provided plugin parameters instead of the document to take care of this.

Example of missing data from s3 docs for Trinity (s3://tempest/watersheds/trinity/trinity-transpo-area-v01/72h/docs/19790201.json):

"metadata": {
    ...
    "watershed_name": "",
    ...
  }

The overwrite thing is done, but may not be necessary for Trinity as @ahdietrich is rerunning

[nick-j-roberts]

Format of ranked document was updated to minimize information being repeated from s3 docs and meilisearch upload function was revised to consume and construct meilisearch formatted documents from these ranked documents

[nick-j-roberts]

Closes #36