Look into leaning into TypeScript more than Prop Types

The Wiki mentions:
> Although the propTypes for the React Components is not required, it will be added gradually in the future for all existing components in FrontEnd. So please start to learn about [type-checking with propTypes](https://reactjs.org/docs/typechecking-with-proptypes.html) add it to your components.

I think the libraries and js world in general have moved to a direction using typescript types more heavily and being able to use it beyond just component props sounds really useful too. Typescript checking can be gradually introduced (similar to prop types), checks on build time (vs run time on prop types). However prop types may be useful for external API data, and from what I can gather, the use cases don't overlap a 100%. It also looks like Prop Types can be inferred from typescript definitions.

Some interesting links I saw:

https://blog.logrocket.com/comparing-typescript-and-proptypes-in-react-applications/

https://stackoverflow.com/questions/41746028/proptypes-in-a-typescript-react-application

The issue does not name specific files, tests, or entry points. Start by reviewing the existing React components and the project's current JavaScript setup, then determine the intended TypeScript adoption scope and how completion would be verified.

Written by the indexing model from the issue text.