fix: standardize error messaging in all service

[rotimi-best]

What does this PR do?

Standardises errors thrown in all service to use our custom error class

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• Enhancement (small improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change adds a new database migration
• This change requires a documentation update

How should this be tested?

• Go into package/lib folder and check for new Error
• No service should contain new Error

Checklist

• Added a screen recording or screenshots to this PR
• Filled out the "How to test" section in this PR
• Read the contributing guide
• 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
• Updated the Formbricks Docs if changes were necessary

[vercel]

@rotimi-best is attempting to deploy a commit to the formbricks Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

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

[mattinannt]

@rotimi-best should we maybe also here throw a new UnknownError with the message of the original error? This way we only through our own errors inside the services. What do you think?

[rotimi-best]

yep that's a good idea

[rotimi-best]

Updated, please let me know what you think.