fix: single use survey not working with email verification

[Dhruwang]

What does this PR do?

Fixes 1685
Also currently single use surveys are broken in general (can fill them multiple times) and its due to a cached service getResponseBySIngleUseId , right now I have removed caching from that service as it is been used at one place only where we dont really require the cached response

How should this be tested?

Take a single use survey with email verification

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		Jan 26, 2024 4:14pm
formbricks-com	⬜️ Ignored (Inspect)	Visit Preview		Jan 26, 2024 4:14pm

[github-actions]

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

[mattinannt]

@Dhruwang thanks for fixing the single use surveys together with email validation 😊🔥 Works great! 😊
But I wasn't really satisfied with removing the cache from the service 😉 The cache itself wasn't the problem and it's good it's there; the issue was that the cache wasn't revalidated correctly. So even a response for the singleUseId for this survey came in, the old cache was used. This could be solved by checking the revalidation strategy of the cache in the specific event (e.g. createResponse).
I re-added the cache and fixed the revalidation in the createResponse 😊