update: Shopify auth connect doc (previously Multipass)

[tamalchowdhury]

This PR updates the Shopify Multipass doc into the new Shopify third-party auth integration guide. It also keeps the legacy Multipass setup in a separate section with a heads-up. Changes the page url from shopify-multipass to kinde-shopify to better align with other guides in this section.

Summary by CodeRabbit

• Documentation
  • Updated Shopify integration guide with Kinde as the identity provider
  • Added instructions for setting up customer authentication using OpenID Connect
  • Reorganized integration documentation with automatic redirect to new location

[coderabbitai]

Warning

Review limit reached

@tamalchowdhury, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db049b8a-e10b-4d27-8f2a-b610329d867c

📥 Commits

Reviewing files that changed from the base of the PR and between f8c1f3b and 37234f0.

📒 Files selected for processing (1)

• astro.config.mjs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tamal/update/shopify-connect-multipass

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details

{}

[pesickaa]

@coderabbitai re-review

[coderabbitai]

@pesickaa, I’ll re-review the latest changes in #755.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[pesickaa]

@tamalchowdhury Looks good to me, fix the merge conflicts and then we just need a Giant to approve

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
17253219	Triggered	JSON Web Token	37234f0	src/content/docs/developer-tools/sdks/frontend/javascript-sdk.mdx	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[cloudflare-workers-and-pages]

Deploying kinde-docs-preview with    Cloudflare Pages

Latest commit:	37234f0
Status:	✅  Deploy successful!
Preview URL:	https://e8bc4081.kinde-docs-preview.pages.dev
Branch Preview URL:	https://tamal-update-shopify-connect.kinde-docs-preview.pages.dev

View logs

[dtoxvanilla1991]

Content checks out - redirect's correct, page_id carried over so related-article links elsewhere don't break, no dangling references to the old slug anywhere in the repo. GitGuardian hit is on an unrelated file on this branch, not something this PR added. Good to merge once the Giant sign-off lands.