fix: upgrade argo-ui components to latest

[agilgur5]

Replaces #11510, fixes all issues I commented about
Fixes #11448 by incorporating argoproj/argo-ui#418

Motivation

• Upgrade to latest version of argo-ui components
  • Upgrade and force resolve other deps to make sure build passes with latest version
• Fix intermediate parameters issue with the overflow fix
• Fix deprecation warnings in build

Modifications

• Pin argo-ui to latest SHA: argoproj/argo-ui@87d27fb

  • Add @types/uuid to fix lack of typing (see chore: upgrade uuid argo-ui#367 and chore: bump argo-ui version argo-cd#13836)
  • Force resolve react-toastify to 9.0.3
    • This was pinned to 9.0.8 in fix: pin react-toastify argo-ui#379 but due to [CRA v4] Can't import the named export 'cloneElement' from non EcmaScript module. PLEASE UPGRADE YOUR CRA VERSION 😿 fkhadra/react-toastify#775, that version is incompatible with Webpack/CRA v4 and was causing errors. Followed this comment to pin to 9.0.3, which fixed the errors
      • Argo CD uses Webpack v5, so I assume that is why they didn't see the same issue
    • Enable esModuleInterop as this was added in Argo UI, and since Argo UI is not compiled (we import source TS), we have to match its tsconfig.json to get the same results
      • This fixes a few import errors (as the errors say)
      • Use default imports for classnames and moment instead of namespace imports to fix the remaining import errors (as the errors suggest)

• Update foundation-sites to fix SCSS deprecation warnings

  • see https://github.com/foundation/foundation-sites/releases/tag/v6.7.0 which had various upgrades and compat fixes

Verification

• Build passes, install succeeds
• Very brief spot check on render, see below comment

[isubasinghe]

Approving it early because CI/UI passes (only really needed to check this). LGTM! Thanks for your work

[agilgur5]

Verification

Build passes, install succeeds

Just noting here that I did not do a full test of rendering the UI, as this my first time touching the UI build process so I still need to figure all that out. From a spot test running yarn start, the UI does render, just with some source map warnings for autolinker (a dep that was not changed and is pinned).

There was one piece of the argo-ui upgrade that was particularly noteworthy, a breaking upgrade of antd: argoproj/argo-ui#387 (comment)

[terrytangyuan]

LGTM

[agilgur5]

react-toastify forced resolution is removed with build upgrades in #11628

[JPZ13]

@terrytangyuan @sarabala1979 - did this PR ever get merged in to a v3.4.x commit? I'm looking through v3.4.16 and don't see it

[agilgur5]

It's not in the 3.4.x changelog and didn't make it into 3.4.11 which is the only release issue back linked above.

I imagine this one might have had cherry-pick issues due to the yarn.lock changes, but idk

[terrytangyuan]

If it's not in changelog then there must have been a conflict. See #11648 (comment) and the comment above and this commit is mentioned as not successfully cherry-picked.