[FEAT-UI]: Update the Hydrograph Page to support saving all inputs and outputs

[martyheynbah]

Make all of the changes necessary to accompany the new integration to save all inputs and outputs. This includes:

• update the run button to always create a new Hydrograph, never update. Also it should kick the user back to the homepage after creating a new run
• Now that there are multiple LCG runs, add a dropdown select input for the user to select the lcg_id to be passed to backend

[noarevalo-bah]

@martyheynbah: update the run button to always create a new Hydrograph, never update.

I'm assuming this is talking about this button, not the save button in the Hydrograph Details pane:

Based on my read, createHydroInput always creates a new row in hydrograph_inputs via the CreateHydrograph handler and service. Can you explicate on this? I think I'm misunderstanding the ask.

Now that there are multiple LCG runs, add a dropdown select input for the user to select the lcg_id to be passed to backend

Continuing to look into how this will eventually work while the PR for this has yet to be merged. Will come back with any more questions

[noarevalo-bah]

Talked with @martyheynbah - these seems to be the desired changes, but will confirm with @trietmnj at noon:

• The stepper creation process should be eliminated (this page):

Use the HydrographDetails view as the base for the creation flow instead, where the user can change the inputs from an existing entry in the hydrograph_inputs table (along with the reach-noaa station associations**) and create a new run (i.e. hydrograph_input and hydrograph lambda job(s)):

To the right of the inputs should be the results of the hydrograph lambda run, whatever they are, similar to the recent changes to the lifecycle generation lambda:

Issues:

• **We don't currently preserve the original reach-noaa station data set on initial hydrograph creation. Reaches are hard deleted. If the goal here is to easily view or use the the original data set for a new hydrograph run in the NoaaInputs map, we'd need to make backend modifications.

• We don't prevent hydrograph creation if reaches aren't assigned to NOAA stations on the frontend. I'm assuming we can look at what is required by the lambda to infer the necessary requirements, but I'll ask.