board: add NanoPi M6 V2 (image + virtual board)

[igorpecovnik]

Adds the NanoPi M6 V2 to the downloads UI.

The M6V2 has no dedicated build — it ships on the unified nanopi6-series
image (R6S/R6C/M6/M6V2) introduced in armbian/build#10442. So it's added as a
virtual board that reuses the nanopi6-series artifacts under its own identity,
plus its board photo.

Changes

• board-images/nanopi-m6v2.png — 1920×1080, transparent background.
  Passes validate-board-assets.sh: 16:9 ✓, resolution ✓, transparent corners ✓,
  opaque fill 42% (≤ 50%) ✓.

• release-targets/reusable.yml — new entry, reusing nanopi6-series on
  both current and vendor branches:

  - board_slug: "nanopi-m6v2"
    board_name: "NanoPi M6 V2"
    board_vendor: "friendlyelec"
    board_support: "conf"
    board_introduced: "2026"
    uses: "nanopi6-series"
    branch: "current,vendor"
    file_extension: "img.xz"

• scripts/generate-armbian-images-json.sh — the reusable-board branch
  filter now accepts a comma-separated list (e.g. current,vendor); an image
  is included if its branch is any of them. A single value keeps its original
  exact-match behaviour, so existing entries are unaffected.

Metadata mirrors nanopi6-series.conf (friendlyelec, conf, 2026). Download
entries appear once nanopi6-series images are published (after #10442 builds).

Verified: reusable.yml parses, generator bash -n clean, and the new filter
tested — current,vendor includes current+vendor and excludes edge; a
single-value filter is unchanged; empty still means all branches.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 29 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4696246-08ad-49c6-b688-b08b2ebb6917

📥 Commits

Reviewing files that changed from the base of the PR and between ee17cda and 5dab638.

⛔ Files ignored due to path filters (1)

• board-images/nanopi-m6v2.png is excluded by !**/*.png

📒 Files selected for processing (2)

• release-targets/reusable.yml
• scripts/generate-armbian-images-json.sh

---

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.}