chore(FDS-389):[Docs]: Fix propTypes for Table

[rociobaena]

Currently, docgen does not have support importing propTypes from external locations.
reactjs/react-docgen#33

There is an external package named https://www.npmjs.com/package/react-docgen-external-proptypes-handler but does not have the full support, the proptype description appears as a custom without a clear reference:

Since this feature is not ready to be used, the propTypes for the table component has been moved to the owner component:

PR Author Checklist

• PR title adheres to Conventional Commits
• I have finished reviewing the contents of this PR for accuracy
• If needed, I have included a Changeset and it follows Semantic Versioning principles
• I have completed all of the above and have enabled auto-merge for this PR

[changeset-bot]

⚠️ No Changeset found

Latest commit: 08a1fd6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/espressive/cascara/5YZEf6VfdmgmS8LL9UF6keMDQSdi
✅ Preview: https://cascara-git-chore-fds-389-show-proptypes-in-table-espressive1.vercel.app

[lordpixel]

@rociobaena thanks for solving this, I know the approach doesn't seem very streamlined but at this point it is the only thing we can do given the circumstances.

Good work and investigation skills 💯

[odiseo42]

looks ok, merging to have a new release ver