Add Jetson video SDK skills to catalog

[adsahu-nv]

Onboarding type

• New product onboarding (new components.d/<slug>.yml file)
• Other (catalog change, README fix, infrastructure, etc.)

For new product onboarding — author affirmations

Not applicable. Jetson Device is already registered in the catalog; this PR adds new skill paths to the existing component.

Reviewer checklist (OSS Skills PIC)

• Author confirmations above are checked
• components.d/<slug>.yml entry valid
• SKILL.md frontmatter spec-compliant
• No new license or third-party dependency requiring OSRB filing

All PRs

• All commits signed off with DCO (git commit -s).

Other context

Registers the following Jetson Video SDK skills from NVIDIA-AI-IOT/jetson-device-skills:

• jetson-video-benchmark
• jetson-video-capability
• jetson-video-pipeline
• jetson-video-recipe
• jetson-video-setup

Each entry maps its source directory to a corresponding top-level catalog directory. The existing automated sync workflow will mirror the skills after this registry change is merged.

[mosheabr]

Approving. Verified against source NVIDIA-AI-IOT/jetson-device-skills (public, NVIDIA-org, not archived).

Scope — this adds 5 skills to the existing jetson-device component rather than onboarding a new product: components.d/jetson-device.yml goes from 9 entries to 14 (+10/-0). The PR body describes this accurately.

Per-skill artifacts — all five carry the full set:

Skill	SKILL.md	skill.oms.sig	skill card	evals/evals.json	BENCHMARK.md
jetson-video-benchmark	yes	yes	yes	yes	PASS
jetson-video-capability	yes	yes	yes	yes	PASS
jetson-video-pipeline	yes	yes	yes	yes	PASS
jetson-video-recipe	yes	yes	yes	yes	PASS
jetson-video-setup	yes	yes	yes	yes	PASS

Each BENCHMARK.md shows real Tier 3 results (2 agents, 11 dimension rows) — no "not available in this report" placeholders.

Other checks — catalog_dir values are globally unique across the catalog and all components.d entries; flat one-entry-per-skill layout with product-prefixed names; frontmatter name matches directory and the descriptions carry trigger keywords; root LICENSE is dual CC-BY-4.0 AND Apache-2.0 with Apache-2.0 declared per skill, which is on the menu; DCO signed off; author and committer both @nvidia.com; no README or generated-file edits.

Note on process, not this PR — the five workflow runs sat at action_required because this is a fork PR and the repo requires approval for all external contributors. I approved them and all five pass. Worth flagging that this affects every fork contributor, and #388 has had its runs unapproved since 30 July.

One small point for future submissions: the affirmations section is marked not applicable because the component already exists. That is technically right, but additions like this still publish new public skills, so the substance of those checks still applies. I verified each independently here and they hold.