[FEAT-API]: Create H5 handlers to process file uploads and reads to S3

[martyheynbah]

Create handlers to:

• GET - Read all H5 files from the s3/ minio instance
• POST - Upload multiple H5 files into the s3/ minio instance
• DELETE - Remove H5 file from s3/ minio instance

[noarevalo-bah]

@Cheng-Kevin2 this comment has some more context around the .txt file with the file naming convention guide on it. might be helpful:

#433 (comment)

Original .txt file (these are included with .h5 file downloads):

06_CHS-SACS_Naming_Convention_Readme_25May2022.txt

[Cheng-Kevin2]

Directory structure within S3 bucket to store h5 files: s3://chart-dev/data/featapi/chs/hydrograph/

[Cheng-Kevin2]

@trietmnj @martyheynbah are there specific paths you want for these endpoints? Such as,

GET - "/project/:projectid/h5/:savepointid"
POST - "/project/:projectid/h5/:savepointid"
PUT - "/project/:projectid/h5/:savepointid"

I added savepointid in case we were thinking about attaching h5 files to savepoints.

[martyheynbah]

No real preference for me, those seem solid

[trietmnj]

From the perspective of the SP to h5 files, the relationship is not 1-to-1 but 1-to-2, and each of the two would have a specific relationship to the SP. i.e, think hashmap, not array.

{
  wave_h5: "stwave_file.h5",
  water_level_h5: "adcirc_file.h5"
}

Not sure if this would maintain the distinction between the wave vs water-level files.