Update metadata

[MVarshini]

This PR fixes the following bugs:

Update metadata API changes
Table Border for select box column
Selecting Saved and New Runs

[dbutenhof]

I'm approving, because catching the dashboard up to the API changes is important (and sorry for missing that when I change the API 😢 ); but I also have some concerns/suggestions/questions ...

[webbnh]

Alternately,

          const errorText = Object.entries(errors).reduce(
            (a, [k, v]) => a += `${k} : ${v} \n`,
            ""
            );

[webbnh]

Alternately,

export const setSelectedSavedRuns = (rows) => (
  {
    type: TYPES.SELECTED_SAVED_RUNS,
    payload: rows,
  }
);

That is, we only need to return a value which is an object -- we don't need any actual code (like a return statement).

[webbnh]

This is expedient, but it would be really handy if we could come up with something less generic. Any context would potentially be helpful.

[webbnh]

The ?. operator needs to be used with considerable care.

For instance, while savedRuns?.length > 0 will "do the right thing" if length is not present, the inverse, savedRuns?.length <= 0, probably won't (that is, they both return false if length is not present, which might be counterintuitive).

Also, we can (and should) use . instead of ?. in the second reference to savedRuns.length, because we know that the field is present if we get past the first test.

So, this code should do an explicit test for the presence of the field, and then test it's value:

    savedRuns?.length && savedRuns.length > 0 && savedRuns.length === selectedSavedRuns?.length;

However, if saved?.length is true-y, then I'm pretty sure that it is greater than zero, so we can omit the middle comparison.

[webbnh]

Just out of curiosity, why are we specifying the style in-line instead of putting it in the .less file?

[webbnh]

We don't need (and therefore shouldn't use) the ?. operator in the second reference.