refactor(StakingProductsCardGrid): update types, logic, and UI composition

[TylerAPfledderer]

Description

This PR overhauls the structure of StakingProductsCardGrid.

• Update types to favor of improved constraints
  • Created type signatures from the stakingProducts json data
  • Alter existing logic and types to match the new constraints
• Code-split UI and logic for improved readability

Related Issue

N/A

[gatsby-cloud]

❌ ethereum-org-website-dev deploy preview failed

Your build failed. View the build logs.

Errors

Your plugins must export known APIs from their gatsby-node.

See https://www.gatsbyjs.com/docs/reference/config-files/gatsby-node/ for the list of Gatsby node APIs.

- The plugin [email protected] is using the API "unstable_shouldOnCreateNode" which is not a known API.

Some of the following may help fix the error(s):

- Rename "unstable_shouldOnCreateNode" -> "shouldOnCreateNode"

Your plugins must export known APIs from their gatsby-node.

See https://www.gatsbyjs.com/docs/reference/config-files/gatsby-node/ for the list of Gatsby node APIs.

- The plugin [email protected] is using the API "unstable_shouldOnCreateNode" which is not a known API.

Some of the following may help fix the error(s):

- Rename "unstable_shouldOnCreateNode" -> "shouldOnCreateNode"

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	32ef36b
🔍 Latest deploy log	https://app.netlify.com/sites/ethereumorg/deploys/660752039cf26500084e3f35
😎 Deploy Preview	https://deploy-preview-11477--ethereumorg.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[wackerow]

This looks great @TylerAPfledderer, thanks! Much cleaner. Working well for me and think we can pull this in.

Left a question on StakingProductCard.tsx, but that doesn't have to block this.

[wackerow]

Is it worth breaking this component apart as well?

[TylerAPfledderer]

@wackerow Hmm I'm not sure. If I continue to break it down, I guess it would be making it's own useHook to abstract away the data and logic. I don't see the usefulness in splitting up the component structure; to me it's not big enough.

I don't think there is enough there right now to justify it unless there becomes an issue in readability.