feat: add missing icons and enforce icon sizes

[sashuk]

FX-4158

Description

According to BASE design (https://www.figma.com/file/TqaGgbpjGSUDf7qq153Isq/Product-Iconography?type=design&node-id=1-2969&mode=design&t=Sz5fcUd1rnrqmlWx-0), icons should always have 16px and 24px versions (https://toptal-core.slack.com/archives/C05CSR5RFBN/p1688574324432869?thread_ts=1687249523.324339&cid=C05CSR5RFBN).

This pull request adds missing icons (taken from BASE) and adds a pre-commit check that makes sure that icon is added.

⚠️ Please note that Ach and CreditCard will be added after they are added to BASE

How to test

• Check the icon list at https://picasso.toptal.net/FX-NULL-add-missing-icons/?path=/story/components-icons--icons
• Try to push incomplete icon locally

Development checks

• Add changeset according to guidelines (if needed)
• Read CONTRIBUTING.md and Component API principles
• Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
• [N/A] Annotate all props in component with documentation
• Create examples for component
• Ensure that deployed demo has expected results and good examples
• [N/A] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
• Self reviewed
• [N/A] Covered with tests

Breaking change

• [N/A] codemod is created and showcased in the changeset
• [N/A] test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

• @toptal-bot run package:alpha-release - Release alpha version
• @toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅

You are OK with merging this PR and

1. You have no extra requests.
2. You have optional requests.
   1. Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌

You are not OK with merging this PR because

1. Something is broken after the changes.
2. Acceptance criteria is not reached.
3. Code is dirty.

When to comment (neither ✅ nor ❌)

You want your comments to be addressed before merging this PR in cases like:

1. There are leftovers like unnecessary logs, comments, etc.
2. You have an opinionated comment regarding the code that requires a discussion.
3. You have questions.

How to handle the comments?

1. An owner of a comment is the only one who can resolve it.
2. An owner of a comment must resolve it when it's addressed.
3. A PR owner must reply with ✅ when a comment is addressed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 82120e8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@toptal/picasso	Major
@toptal/picasso-charts	Major
@toptal/picasso-forms	Major
@toptal/picasso-rich-text-editor	Major
@topkit/analytics-charts	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[sashuk]

@toptal-anvil ping reviewers

[sashuk]

@toptal-anvil ping reviewers

[mkrl]

Love the pre-commit hook rule! I have one idea on how to improve it, but it's not too critical (even though pretty nice to have).

[sashuk]

@toptal-anvil ping reviewers