(WIP) Remove PrimaryButton.tsx and SecondaryButton.tsx and DangerButton.tsx & update places they are used

[jtucholski]

This issue was refactored out of a previous issue to look at the usage of PrimaryButton, SecondaryButton, and DangerButton and refactor them accordingly.

• PrimaryButton.tsx and SecondaryButton.tsx are really old components and should no longer be used. In many places now, specifically for forms, we use SubmitButton.tsx, but a new component should be created for more general cases.
• Clarification needed before turning into ticket
  • Decide on a look for buttons that are not submit. Ideally these would look slightly different as they have different functionalities, but some more research might be helpful on best UI practices.

[jtucholski]

@calisio I think that this is something you brought up in a different ticket when we discussed some refactoring. Without digging too deep, do you know of any more context that we should add to this issue right now?

[calisio]

The places that these buttons are used should instead use the class button and it should apply the necessary styling. There are several examples (such as the Add Provider button on provider platforms) that it should look like. Please do not use btn btn- classes, these are daisy ui styling we want to move away from!!