feat + refactor: added messenger sharing

[UnknownSean8]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have run the tests for the backend and frontend depending on what's needed for my changes as described in the testing section of the contributing guide

---

Description

Refactored the buttons from the share page as a component and added messenger sharing to the modal. Lmk what do you think about the refactoring, thanks!

Related issue

• Add Facebook Messenger to Modal Share Page Component #698

[netlify]

✅ Deploy Preview for activist-org ready!

Name	Link
🔨 Latest commit	11cbd5d
🔍 Latest deploy log	https://app.netlify.com/sites/activist-org/deploys/676520e8ad51c10008e22640
😎 Deploy Preview	https://deploy-preview-1070--activist-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Thank you for the pull request!

The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

• The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

• The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Will pick this up and bring it in tomorrow morning, @UnknownSean8 :) If you have an idea on the failing frontend tests, then let us know. Specifically the type check errors in pages/organizations/[id]/events.vue.

[andrewtavis]

Was what I was thinking too, but also weird that it's not needed for groups 🤔

[UnknownSean8]

Mhm, I'll take a look at the groups later after work.

[UnknownSean8]

Oh, it's because the Events type was previously under the dom-events type by default, but since there is no default type for groups, it's defined as an any. The any type wouldn't have any problem under this case.

[andrewtavis]

Ah ok, so we'll need to switch it up eventually. Thanks for checking that! 🚀

[andrewtavis]

Thanks much for the refactor and the frontend fixes, @UnknownSean8! Really great to have all of this so well structured :) Will make future work like #904 a lot easier 😊