Publish 2.216.0 version with peerDependencies properly defined

[ulziibay]

Jira: SECNG-1644

Overview:

For npm7+ to properly install this package, the peerDependency list must be properly defined as explained in https://github.com/npm/rfcs/blob/main/implemented/0025-install-peer-deps.md. For example, this was needed to be able install this package using npm9 within SD2 in https://github.com/Clever/sd2/pull/6203.

Additionally, moved the @types packages to dependency from devDependency for correctness.

Screenshots/GIFs:

Testing:

• Unit tests
• Manual tests:
  • Chrome
  • Safari
  • IE11

Roll Out:

• Before merging:
  • Updated docs
  • Bumped version in package.json
    • Breaking change?
      • If it is a beta component run npm version minor
      • If the component is not in beta run npm version major
    • New component or backward-compatible component feature change? Run npm version minor
    • Only changing documentation? All good. Skip this step.
  • After creating a new component, make sure to add it to the Components List in ComponentsView.jsx. To do so:
    • Add a screenshot of the component in docs/assets/img with the format <COMPONENT URL LINK>.png
• After merging:
  • Deployed updated docs (make deploy-docs)
  • Posted in #eng if I made a breaking change to a beta component