Added support/troubleshooting and support/faq articles

[drvarmin]

Add new support documentation

This PR adds three new support articles to improve AI-assisted answers and help users troubleshoot common issues.

New Documentation

1. Migration Guide

File: content/docs/support/faq/how-to-migrate-from-another-provider-to-superwall.mdx

Covers migrating from Adapty, Qonversion, Glassfy, or other subscription SDKs to Superwall, including what data migrates automatically and what doesn't.

2. Subscription Status vs Dashboard Data

File: content/docs/support/troubleshooting/subscription-status-active-but-no-dashboard-data.mdx

Explains why a user may have an active subscription on device but no entitlements, Apple events, or webhooks in the dashboard (user ID attribution mismatch after reinstall).

3. Paywall Not Updating After Publishing

File: content/docs/support/troubleshooting/why-is-my-paywall-not-updating-after-publishing.mdx

Comprehensive troubleshooting guide for when users still see outdated paywalls after publishing changes. Covers sticky A/B test assignments, conditional visibility, caching behavior, and more.

---

AI Response Comparison (Local with new docs vs Remote/Production)

Query: "I want to migrate from Adapty to Superwall, what do I need to do?"

Local (with new docs):

To migrate from Adapty to Superwall, you'll need to follow these steps:

1. Remove the Previous SDK: Uninstall the Adapty SDK from your project.
2. Install the Superwall SDK: Follow Superwall's installation guide for your platform.
   ...

How to migrate from another provider to Superwall

Remote (production):

I'm not sure about this. Please check with further resources.

---

Query: "SDK shows subscription is active but I can't see any purchase data or server events in the dashboard for this user"

Local (with new docs):

This is expected behavior and not a bug. The SDK determines subscription status from the local Apple receipt, which is tied to the user's Apple ID. The dashboard, however, attributes subscription data to a specific Superwall user ID at the time of purchase. If a subscription was purchased under a different Superwall user ID than the one currently being viewed in the dashboard, the SDK will show an active subscription on the device, but no corresponding data will appear in the dashboard for the current user ID.

Why Does My User Show Active Subscription Status But No Entitlements in the Dashboard?

Remote (production):

This can happen if you are using a PurchaseController and it is not correctly configured... (incorrect diagnosis)

---

Query: "I updated my paywall and published it but users still see the old version"

Local (with new docs):

If users are still seeing an old version of your paywall after you've updated and published it, there are several factors to consider.

First, ensure the paywall was actually published...
Second, if your campaign uses multiple paywalls in an A/B test, users are assigned to a variant, and this assignment is "sticky"...
Third, conditional visibility and dynamic values can cause different content to show...
Fourth, check the product configuration...
Finally, caching can play a role...

Why is my paywall not updating after publishing?

Remote (production):

Changes you make to a paywall are saved locally, but to make them live for users, you must click the Publish button... (incomplete answer, missing key causes)