Add Community tag to plugins

[yakkomajuri]

Changes

Please describe.
If this affects the frontend, include screenshots.

I guess this conflicts with #2965 but just bringing this up because it's important to differentiate core team vs community plugins here too so users are aware of what they're installing and we can be more liberal with accepting community plugins into the list.

Style is consistent with the website plugin library.

Checklist

• All querysets/queries filter by Organization, by Team, and by User
• Django backend tests
• Jest frontend tests
• Cypress end-to-end tests

[paolodamico]

Some post-facto feedback on this, if it leads somewhere I can move it to an issue.

Please push back, but not a big fan of doing "Core Team" as this a) either gives me a vibe of a hobby project or b) is something that only an engineer that's familiar with OSS terminology will understand. I think it'd be better to do something that conveys an "official" vibe. Keeping it standardized maybe we could try something like we do for PostHog properties? Or maybe it's just as simple matter as changing the label.

Probably out of scope for this PR, but should there be a third category, something like community but verified?

CC @mariusandra, @yakkomajuri just some thoughts

[mariusandra]

Why not "Official" vs "Community"?

[paolodamico]

Think that works well for now 👌