[bot] sync troubleshooting guides to db (#32879)

Co-authored-by: github-docs-sync-bot <github-docs-sync-bot@supabase.com>

apps/docs/content/troubleshooting/google-auth-fails-for-some-users-XcFXEu.mdx

@@ -2,11 +2,12 @@
 title = "Google Auth fails for some users"
 github_url = "https://github.com/orgs/supabase/discussions/14883"
 date_created = "2023-06-07T20:38:48+00:00"
-topics = ["auth"]
-keywords = ["OAuth", "Google", "credential", "email"]
+topics = [ "auth" ]
+keywords = [ "OAuth", "Google", "credential", "email" ]
+database_id = "1ea7b605-dc1d-43d8-a365-5bc2801dd90e"
 
 [api]
-sdk = ["supabase.auth.signInWithOAuth"]
+sdk = [ "supabase.auth.signInWithOAuth" ]
 
 [[errors]]
 http_status_code = 500

apps/docs/content/troubleshooting/how-do-i-check-gotrueapi-version-of-a-supabase-project-lQAnOR.mdx

@@ -2,7 +2,8 @@
 title = "How do I check GoTrue/API version of a Supabase project?"
 github_url = "https://github.com/orgs/supabase/discussions/14217"
 date_created = "2023-05-09T04:21:49+00:00"
-topics = ["auth", "platform"]
+topics = [ "auth", "platform" ]
+database_id = "74972531-f2fc-4d68-a745-21f9c75761e6"
 ---
 
 Make a `GET` request to the health check endpoint to retrieve this information. Below is an example using `curl`:

apps/docs/content/troubleshooting/how-do-i-make-the-cookies-httponly-vwweFx.mdx

@@ -2,8 +2,9 @@
 title = "How do I make the cookies HttpOnly?"
 github_url = "https://github.com/orgs/supabase/discussions/18869"
 date_created = "2023-11-10T11:49:06+00:00"
-topics = ["auth"]
-keywords = ["cookies", "HttpOnly"]
+topics = [ "auth" ]
+keywords = [ "cookies", "HttpOnly" ]
+database_id = "cdaa76a4-3e5b-4c8f-82f0-b713c4cf19ab"
 ---
 
 This is not necessary. Both the access token and refresh token are designed to be passed around to different components in your application. The browser-based side of your application needs access to the refresh token to properly maintain a browser session anyway.

apps/docs/content/troubleshooting/how-to-migrate-from-supabase-auth-helpers-to-ssr-package-5NRunM.mdx

@@ -2,8 +2,9 @@
 title = "How to Migrate from Supabase Auth Helpers to SSR package"
 github_url = "https://github.com/orgs/supabase/discussions/27849"
 date_created = "2024-07-07T17:24:30+00:00"
-topics = ["auth"]
-keywords = ["migration", "auth", "ssr", "package"]
+topics = [ "auth" ]
+keywords = [ "migration", "auth", "ssr", "package" ]
+database_id = "273b79ad-b8ff-4669-8544-b99920e2d3c8"
 ---
 
 The `auth-helpers` packages are being deprecated and replaced with the `@supabase/ssr` package. We recommend migrating to the `@supabase/ssr` package as future bug fixes and feature releases are focused on the `@supabase/ssr` package.

apps/docs/content/troubleshooting/i-am-not-receiving-password-reset-emails-for-supabase-dashboard--cO5yf.mdx

@@ -2,8 +2,9 @@
 title = "I am not receiving password reset emails for Supabase dashboard"
 github_url = "https://github.com/orgs/supabase/discussions/14043"
 date_created = "2023-04-30T08:08:07+00:00"
-topics = ["auth", "platform"]
-keywords = ["email", "reset"]
+topics = [ "auth", "platform" ]
+keywords = [ "email", "reset" ]
+database_id = "ec816bde-1a27-461f-89ef-211e96810dd9"
 ---
 
 Most likely, you signed up on Supabase using a GitHub account. Please try the GitHub login method to see if you can log in. If you still cannot log in, please write to support@supabase.com using your email with a screenshot of the error from the dashboard.

apps/docs/content/troubleshooting/rotating-anon-service-and-jwt-secrets-1Jq6yd.mdx

@@ -2,8 +2,9 @@
 title = "Rotating Anon, Service, and JWT Secrets"
 github_url = "https://github.com/orgs/supabase/discussions/20031"
 date_created = "2023-12-27T14:54:11+00:00"
-topics = ["auth", "platform"]
-keywords = ["jwt", "secrets", "key", "security"]
+topics = [ "auth", "platform" ]
+keywords = [ "jwt", "secrets", "key", "security" ]
+database_id = "caa72a34-696c-47c6-8976-e50cf7fb396e"
 ---
 
 Has this ever been you: "Oh no! I accidentally committed my service key to our public repo!" Or maybe rotating keys is just something you regularly do for security compliance.