chore: migrate react components from babel / webpack to vite

[christjt]

Type of change

Description 📝

How has this been tested? 🔍

Manually tested build output in FDX, manually tested storybook. Also compared build output bundle size to make sure there are no regressions.

Test instructions ℹ️

• Building still works
• Storybook still works (with hot module reload)
• There are no performance regressions when building the package or serving storybook
• Running the command yarn run build:watch:yalc and yarn link ... in FDX properly sets up a flow where changes in react components are automatically propagated to FDX without any additional commands needed

NOTE ON LAST POINT: linking this package into FDX will have some issues since yarn in FDX will not respect new dependencies in reveal react components. So for this test you will need to yalc add -> yarn install in FDX then yalc link. This awkward step will not be nessesary once the actual npm package published has been updated in FDX. This is not a regression and was how it worked previously as well, it is simply noticable now in this PR since I had to change some deps.

Checklist ☑️

• I am proud of this feature.
• I have performed a self-review of my own code.
• I have added PR type (Feat, Bug, Chore, Test, Docs, Style, Refactor) to the PR title.
• I have manually tested this for different scenarios (different models, formats, devices, browsers).
• I have commented my code in hard-to-understand areas.
• I have made corresponding changes to the public documentation.
• I have added unit and visuals tests to prove that my feature works to the best of my ability.
• I have refactored the code for readability to the best of my ability.
• I have checked that my changes do not introduce regressions in the public documentation.
• I have outlined any known defects / lacking capabilities in the contents of this PR.
• I have listed any remaining work that should follow this PR in the description or jira/miro/etc.
• I have added TSDoc to any public facing changes.
• I have added "developer documentation" in any package README.md that is related / applicable to this PR.
• I have noted down and am currently tracking any technical debt introduced in this PR.
• I have thoroughly thought about the architecture of this implementation.
• I have asked peers to test this feature.

[Savokr]

Feels really good! Very decent upgrade in terms of build speed and especially linking with FDX works really smooth!