docs(source-facebook-pages): improve OAuth permissions documentation

[devin-ai-integration]

What

Improves the OAuth permissions documentation for the Facebook Pages source connector by:

• Adding read_insights to the required permissions list (needed for Page Insights and Post Insights streams)
• Separating core required permissions from additional permissions needed for all Page stream fields
• Fixing minor typo ("The" → "the")

This change was prompted by reviewing commit a4bfeec which added the OAuth App section.

How

Reorganized the permissions list in docs/integrations/sources/facebook-pages.md to distinguish between:

1. Core permissions needed for basic connector functionality: pages_read_engagement, pages_read_user_content, pages_show_list, read_insights
2. Additional permissions needed to sync all fields from the Page stream: pages_manage_ads, pages_manage_metadata, catalog_management

Review guide

1. docs/integrations/sources/facebook-pages.md - Verify the permission categorization is accurate based on Facebook Graph API requirements

User Impact

Users creating their own OAuth App will have clearer guidance on which permissions are required for basic functionality vs. which are needed for advanced features.

Can this PR be safely reverted and rolled back?

• YES 💚

---

Link to Devin run: https://app.devin.ai/sessions/50dcafdaac264bad82044c5b3dad8b0d
Requested by: unknown ()

Note: I was unable to verify the Docusaurus build locally due to pre-existing environment issues with the postman-code-generators package. The documentation change is minimal and unlikely to cause broken links.

[devin-ai-integration]

Original prompt from API User

Please use playbook macro: !connectordocs\n\nThe commit to review is a4bfeecdac84b6314a2d9e138513ee66a5292049. This commit was pushed to master and may contain connector changes that need documentation updates.

PLAYBOOK_md:
## Overview

The goal of this task is to update Airbyte's end user documentation for a connector. A change has been merged to master in GitHub for that connector. Updated documentation might be necessary, since documentation quality can vary from connector to connector.

## Your role

You are Technical Writer Devin. You write clear, concise, and accurate technical documentation for end users of Airbyte. Your audience consists of data engineers who are using Airbyte to move data from one location to another. Some readers are less technical and some are more technical. Assume you are writing for someone who is less technical so all audiences can still follow your instructions, but don't patronize or look down upon your readers.

## Your task

1. Review the source code for the Airbyte connector described in this change.
         
2. To improve your context, search the web and read the official third-party API documentation for the product this connector works with. Not all third parties have public documentation, but most do. If you can't find the right documentation, ignore this step.
            
3. Find the user documentation for this connector. It's in the airbyte repository, in the /docs/integrations folder. Review this documentation. Based on the research you did in steps 1 and 2, create a new branch and propose any necessary improvements to this documentation. Perform this action in the following steps: Fix information that is technically incorrect. Then add information that isn't documented, but is necessary or helpful when trying to operate the connector. Then remove information that is irrelevant, outdated, or repeated. Then correct spelling and grammar mistakes.
            
4. Build the Docusaurus site locally using `pnpm clear` and `pn... (3281 chars truncated...)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Live Tests
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
  • You can specify a custom changelog by passing changelog. Example: /bump-version changelog="My cool update"
  • Leaving the changelog arg blank will auto-populate the changelog from the PR title.
• /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
• /run-live-tests - Runs live tests for the modified connector(s).
• /run-regression-tests - Runs regression tests for the modified connector(s).
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
• /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-dev.{git-sha}) for all modified connectors in the PR.
• JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
  • /bump-bulk-cdk-version bump=patch changelog='foo' - Bump the Bulk CDK's version. bump can be major/minor/patch.
• Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.

📝 Edit this welcome message.

[devin-ai-integration]

@ian-at-airbyte I am an AI (Devin) and have proposed documentation updates based on recent changes to the source-facebook-pages connector (specifically commit a4bfeec).

The changes improve the OAuth permissions documentation by:

1. Adding read_insights to the required permissions list (needed for Page Insights and Post Insights streams)
2. Separating core required permissions from additional permissions needed for all Page stream fields

You can merge this PR, modify it, or close it if you disagree with the changes.

Note: I was unable to verify the Docusaurus build locally due to pre-existing environment issues with the postman-code-generators package. The documentation change is minimal and unlikely to cause broken links.

[github-actions]

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-rhobnm9ab-airbyte-growth.vercel.app

Built with commit 1948dc3.
This pull request is being automatically deployed with vercel-action