docs: add missing table permissions section to Vue tutorial

[KesleyDavid]

What does this PR do?

The Vue idea tracker tutorial (step 6, Add database) never explains how to configure table permissions. Readers following the tutorial step by step get authorization errors when listing or creating ideas, and the app only works after manually figuring out permissions in the Console.

This PR adds a Configure permissions section to the Vue tutorial's step 6 (src/routes/docs/tutorials/vue/step-6/+page.markdoc), mirroring the section that already exists in the React and React Native versions of the same tutorial (same shared screenshots, same wording, same heading ID convention).

Test Plan

Verified locally with Bun 1.3.14 (same major version as CI) on macOS arm64:

• bun install --frozen-lockfile — clean
• bun run check (svelte-check) — 0 errors, 0 warnings
• bun run format:check (prettier) — All matched files use Prettier code style
• bun run build — builds successfully (observed an intermittent node-fetch-native-with-agent worker error in Bun on cold runs; it also occurs on an unmodified main checkout and is unrelated to this change — repeated runs pass consistently)

Also verified:

• The added section matches the existing React (src/routes/docs/tutorials/react/step-6/+page.markdoc) and React Native (src/routes/docs/tutorials/react-native/step-6/+page.markdoc) tutorials
• Both referenced screenshots already exist in the repo (static/images/docs/tutorials/idea-tracker-permissions.avif and the dark variant)
• The Markdoc structure (heading ID, {% only_dark %}/{% only_light %} blocks) matches sibling pages

Related PRs and Issues

Closes #1467

Have you read the Contributing Guidelines on issues?

Yes — including the website repo's CONTRIBUTING.md and STYLE.md, and the Code of Conduct.

---

🤖 This PR was prepared with AI assistance (Kimi Code CLI), reviewed and verified by the author before submission.

[greptile-apps]

Greptile Summary

The PR adds the missing table-permission setup to step 6 of the Vue idea-tracker tutorial.

• Documents table-level Read and Create permissions.
• Adds light and dark permission screenshots.
• Instructs readers to enable row security and save the configuration.

Confidence Score: 4/5

The PR should not merge until the permission instructions or row-creation example preserve the creator's ability to delete their ideas.

Enabling row security leaves newly created rows without owner delete permission, even though the next tutorial step exposes an owner-only Remove action.

Files Needing Attention: src/routes/docs/tutorials/vue/step-6/+page.markdoc

Important Files Changed

Filename	Overview
src/routes/docs/tutorials/vue/step-6/+page.markdoc	Adds permission configuration guidance, but enabling row security without adding owner permissions breaks the tutorial's delete flow.

Prompt To Fix All With AI

### Issue 1
src/routes/docs/tutorials/vue/step-6/+page.markdoc:36
**Row security breaks deletion**

When a signed-in user creates an idea and clicks its owner-only Remove button, row security is enabled but `createRow` assigns no row-level delete permission, causing `deleteRow` to return an authorization error.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "docs: add missing table permissions sect..." | Re-trigger Greptile}

[greptile-apps]

Row security breaks deletion

When a signed-in user creates an idea and clicks its owner-only Remove button, row security is enabled but createRow assigns no row-level delete permission, causing deleteRow to return an authorization error.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/routes/docs/tutorials/vue/step-6/+page.markdoc
Line: 36

Comment:
**Row security breaks deletion**

When a signed-in user creates an idea and clicks its owner-only Remove button, row security is enabled but `createRow` assigns no row-level delete permission, causing `deleteRow` to return an authorization error.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.