feat: sync endpoint error handling

[pandeymangg]

What does this PR do?

Adds a new status field to the TJsConfig type, which indicates that the formbricks js sdk is in an error state. Its set after a sync call fails and then the initialize function checks for the error state to skip initialization

Fixes # (issue)

How should this be tested?

• Fail the sync call, throw an error from the api route for example.
• There should be no unnecessary sync calls

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

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		Mar 2, 2024 10:48am
formbricks-com	⬜️ Ignored (Inspect)	Visit Preview		Mar 2, 2024 10:48am

[github-actions]

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

[review-agent-prime]

packages/js/src/lib/initialize.ts

Consider using a more descriptive variable name than 'e' for the error object in the catch block. This will improve the readability of your code and make it easier for others to understand.
Create Issue
See the diff
Checkout the fix

    try {
      existingConfig = config.get();
    } catch (error) {
      logger.debug("No existing configuration found.");
    }

git fetch origin && git checkout -b ReviewBot/Impro-fswczsv origin/ReviewBot/Impro-fswczsv

[mattinannt]

@pandeymangg Thank you for the PR 😊💪 I changed a few things up:

• When formbricks-js enters the error state it gets deinitialized. This makes our status management easier as formbricks-js can't be initialized and in an error state
• The error state management doesn't happen in the sync but in the functions that use the sync. that makes it easier to handle the different cases and we don't bloat the sync function with different checks.
• As we currently have some users sending a lot of attributes, I also removed the sync after changing an attribute.