Clean up how we use links

[rchlfryn]

Description

This PR cleans up for we use Button and CMSLink components. We currently use buttons in 3 different ways:

1. CMSLink - a guided way for a user to choose a link form a collection. Looks like a button but is rendered as an a tag
2. Link + Button - a link to another page or action
3. Button - not a link but performs an action

---

From the linked issue:

This issue should consider the best approach to using links with button styling that also capture events.

I assume the second part of this is referring to Posthog events. All link clicks are autocaptured by posthog.

Related Issues

Resolves #685

Key Changes

• Add ButtonLink component since we were repeating the components pattern
• Removed unused button variants destructive and link
• Updated EventTable and EventPreview to use proper Button component instead of incorrectly used CMSLink
• Adds clearIrrelevantLinkValues to linkField
• Refactors linkToPageOrPost to linkField
  • Needed to keep linkToPageOrPost for quickLinks config since the type is array instead of group
• Clean up defaultLexical url validation
• Updated coding guide

How to test

There should be no visual differences

Future enhancements / Questions

We could use linkField in navLink, since the configs are identical. Using linkField will change newTab to be the second column which will cause a migration that will create a new table and drop the old one which seems invasive for the change. Do we want to do this?

[github-actions]

Preview deployment: https://link-cleanup.preview.avy-fx.org

[rchlfryn]

I did not copy this over as it is not necessary.