docs(source-youtube-data): Update stream descriptions to reflect expanded schema data

[devin-ai-integration]

What

Updates the YouTube Data connector documentation to accurately reflect the expanded data now available after the schema fixes in PR #71016. Also fixes an incorrect PR number in the changelog.

This PR was created by Devin at the request of an automated documentation review task.

Link to Devin run: https://app.devin.ai/sessions/9be64beb7dbf49daa3cd51242a0ea192

How

1. Updated the video stream description to document all available data: snippet information, content details (duration, dimension, definition, caption availability, region restrictions), statistics (view/like/comment counts), player information (embed HTML), and status (upload status, privacy status, license, embeddable, made for kids).

2. Updated the channels stream description to document all available data: snippet information, content details (related playlists), statistics, branding settings, topic details, status, localizations, and content owner details.

3. Fixed the changelog entry for version 0.0.44 which incorrectly displayed "70971" but linked to PR 71016.

4. Added trailing pipes to changelog table rows for consistent markdown table formatting (per reviewer feedback).

Review guide

1. docs/integrations/sources/youtube-data.md - Verify the stream descriptions accurately reflect the data available in the connector's manifest.yaml

User Impact

Users will have more accurate documentation about what data is available from the YouTube Data connector's video and channels streams.

Can this PR be safely reverted and rolled back?

• YES 💚

Important

Auto-merge enabled.

This PR is set to merge automatically when all requirements are met.

[devin-ai-integration]

Original prompt from API User

Please use playbook macro: !connectordocs

The commit to review is 88575185d1a13cf9ac7a59e9818d4ada9b34dc49. 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 `pnpm... (3279 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 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.
• /bump-progressive-rollout-version - Bumps connector version with an RC suffix for progressive rollouts.
  • Creates a release candidate version (e.g., 2.16.10-rc.1) with enableProgressiveRollout: true
  • Example: /bump-progressive-rollout-version changelog="Add new feature for progressive rollout"
• /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
• /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}-preview.{git-sha}) for all modified connectors in the PR.
• Connector release lifecycle (AI-powered):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-release-watch - Monitors rollout post-release and tracks sync success rates.
• 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]

Hi @ian-at-airbyte,

I am Devin, an AI assistant. I have proposed documentation updates for the YouTube Data connector based on recent changes in commit 8857518 (PR #71016).

Summary of changes:

• Updated the video stream description to document all available data fields now included after the schema fixes (content details, statistics, player information, and status)
• Updated the channels stream description to document all available data fields (branding settings, topic details, status, localizations, and content owner details)
• Fixed the changelog entry for version 0.0.44 which incorrectly displayed "70971" but linked to PR 71016

Please feel free to merge this PR if the changes look good, modify it as needed, or close it if you disagree with the proposed updates.

[github-actions]

Deploy preview for airbyte-docs ready!

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

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

[ian-at-airbyte]

Devin can you address the inconsistent table pipe usage please.

[devin-ai-integration]

Done! I've added trailing pipes to the changelog table rows for lines 0.0.44 and 0.0.43 to ensure consistent table formatting.