Remove PaymentForm, CardForm, and BankAccountForm from Storybook

[jakemer]

We have several components in Storybook currently which are used in payments processing, however our recommended route is to use the Checkout component going forward. Therefore we would like to not have other payment/payment method related components in Storybook as it causes confusion and documentation overhead.

Developer considerations

• On any task
  • [ ] Previous unit and e2e tests are passing
  • [ ] Perform dev QA
• On new features
  • [ ] Add unit tests
  • [ ] Add e2e tests
  • [ ] Add documentation
  • [ ] Does the component have exportedparts for styling? If so, add unit a unit test for each exportedpart
• On bugs
  • [ ] Add unit tests to prevent the bug from happening again

Developer QA steps

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 4edaeb5b32c0898907fb971d13869699f0f6cc27

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

[TiagoFuelber]

@jakemer Just a question I have, will the PaymentForm be still available, will it be deleted?