feat(nx-dev): move openai call to edge function

[mandarini]

Moved the OpenAI API calls into a Next.js Edge function, so that the API key is not revealed to the client!

test it here: https://nx-dev-git-fork-mandarini-feat-move-openai-call-to-edge-nrwl.vercel.app/ai

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 24, 2023 11:20am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit c36c59c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• linux nx affected --target=e2e --base=72fc94b3f24bedc4a7f0bf0f45138755a675059f --head=c36c59c3231e715013c85b1dd52a3502163ec7e4 --parallel=1
• linux nx affected --target=build --base=72fc94b3f24bedc4a7f0bf0f45138755a675059f --head=c36c59c3231e715013c85b1dd52a3502163ec7e4 --parallel=3
• linux nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• linux nx affected --target=test --base=72fc94b3f24bedc4a7f0bf0f45138755a675059f --head=c36c59c3231e715013c85b1dd52a3502163ec7e4 --parallel=1
• linux nx affected --target=lint --base=72fc94b3f24bedc4a7f0bf0f45138755a675059f --head=c36c59c3231e715013c85b1dd52a3502163ec7e4 --parallel=3
• nx-cloud record -- nx format:check --base=72fc94b3f24bedc4a7f0bf0f45138755a675059f --head=c36c59c3231e715013c85b1dd52a3502163ec7e4
• linux nx documentation --no-dte
• macos nx affected -t e2e-macos --parallel=1 --base=72fc94b3f24bedc4a7f0bf0f45138755a675059f --head=c36c59c3231e715013c85b1dd52a3502163ec7e4

---

Sent with 💌 from NxCloud.

[ndcunningham]

{
    "code": "42501",
    "details": null,
    "hint": null,
    "message": "new row violates row-level security policy for table \"user_queries\""
}

I got this error when running the preview.
Is this something we should handle?

Found an error

[ndcunningham]

Do we need to handle supabase calls as well?

[mandarini]

@ndcunningham RE: supabase: I don't think we need to handle the Supabase stuff, because @FrozenPandaz added the anon key there, which is ok to be revealed?

[mandarini]

@ndcunningham the feedback error is expected, because we changed some things with permissions. Next week I'll work on the new feedback functions, and it will be fixed!

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.