feat: website surveys

[pandeymangg]

What does this PR do?

Introduces a new survey type website, replaces the previous surveys typed as web to website and inApp using a data migration. Splits the js-package into two different exports in favour of js/website and js/in-app. Handles the UI changes and the package bundling changes and the database changes.

How should this be tested?

• Create a new survey and look at the survey types, there should be a new website survey type.
• Website surveys can be tracked in the demo app on the /website page.
• The js package is split into js/website and js/in-app.

Checklist

Required

• Filled out the "How to test" section in this PR
• Read How we Code at Formbricks
• Self-reviewed my own code
• Commented on my code in hard-to-understand bits
• Ran pnpm build
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues
• First PR at Formbricks? Please sign the CLA! Without it we wont be able to merge it 🙏

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Formbricks Docs if changes were necessary

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
formbricks-cloud	⬜️ Ignored (Inspect)	Visit Preview		Apr 23, 2024 1:04pm
formbricks-com	⬜️ Ignored (Inspect)	Visit Preview		Apr 23, 2024 1:04pm

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏

[mattinannt]

@pandeymangg Looks great! :-) 🚀
Can you please do the following before the merge:

• Solve the merge conflicts and move the data migration to the new data-migrations folder
• Rename in-app to app (as well as InApp->App, etc.). This way we have cleaner types and package names without hyphens :-)