Integrate posthog in frontend

[joanagmaia]

Changes proposed ✍️

• Add posthog-js lib to frontend and initialize it with API key
• Created a method to check if feature flag value is enabled
• Updated configs to check community and premium versions
• Added feature flag validation for:
  • Organizations page -> if not show restricted access page
  • Eagle eye page -> if not show restricted access page
  • Community Help Center page -> if not show free badge, disable custom domain url and add a CTA that leads to show restricted access page
  • Automations page -> if not, when clicked on Add automation, show restricted access page

NOTE: Cannot be merged before #318

Checklist ✅

• Label appropriately with Feature, Enhancement, or Bug.
• Tests are passing.
• New backend functionality has been unit-tested.
• Environment variables have been updated:
  • Local frontend configuration: frontend/.env.dist.local, frontend/.env.dist.composed.
  • Local backend: backend/.env.dist.local, backend/.env.dist.composed.
  • Configuration docs have been updated.
  • Team members only: update environment variables in override, staging and production env. files and trigger update config script.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.
• All changes have been tested in a staging site.
• All changes are working locally running crowd.dev's Docker local environment.

[mariobalca]

Awesome job here @joanagmaia 🙌
Left a minor comment, but shouldn't be a blocker.
Will try to QA this a bit in local/staging, during the afternoon 👍

[mariobalca]

Are these the only changes we need to include related to plans?
We also have the plans.js file, which we should also update I think

[joanagmaia]

Sorry I forgot to mention but both permissions and plans file were updated in Anil's PR https://github.com/CrowdDotDev/crowd.dev/pull/318/files#diff-0e09062fc2c86ce9490bfbd2117e20613eb73e9cb7e7c7232a879213e76696d6

This one cannot be deployed without that PR. Given that this branch does not include backend changes, to test it locally you will either need to test it in staging branch or run with the backend from the feature/tenant-plans-and-feature-flagging branch

[mariobalca]

I see! Thanks for clearing that out, makes sense!