fix: async data prep functions should use Promise.resolve

[stefl]

Description

• These data prep functions for exports are marked as async
• Use Promise.resolve to retain the expected async behaviour without changing the signature of each function
• Not user-facing

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
oak-ai-lesson-assistant	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 10, 2025 1:25pm

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Playwright test results

 17 passed
 2 skipped

Details

 Open report ↗︎
 19 tests across 16 suites
 2 minutes, 48 seconds
 c7cff2c

Skipped tests

No persona › tests/auth.test.ts › authenticate through Clerk UI
No persona › tests/chat-performance.test.ts › Component renders during lesson chat › There are no unnecessary rerenders across left and right side of chat

[codeincontext]

Use Promise.resolve to retain the expected async behaviour without changing the signature of each function

I think this is an issue in linting, as the behaviour in both cases is identical. As far as I know, returning Promise.resolve in an async function is a no-op, the goal in this PR is to fix the lint warnings saying "this is an async function and it doesn't look like it needs to be"

[oak-machine-user]

🎉 This PR is included in version 1.21.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀