vscode: move Pull Requests section below Backlog in the sidebar default order

[amrmelsayed]

Proposal

Swap the default order of the Pull Requests and Backlog sections in the Codev sidebar.

Current order (packages/vscode/package.json)

"views": {
  "codev": [
    { "id": "codev.workspace",       "name": "Workspace" },
    { "id": "codev.builders",        "name": "Builders" },
    { "id": "codev.pullRequests",    "name": "Pull Requests" },
    { "id": "codev.backlog",         "name": "Backlog" },
    { "id": "codev.recentlyClosed",  "name": "Recently Closed" },
    { "id": "codev.team",            "name": "Team", "when": "codev.teamEnabled" },
    { "id": "codev.status",          "name": "Status" }
  ]
}

New order

"views": {
  "codev": [
    { "id": "codev.workspace",       "name": "Workspace" },
    { "id": "codev.builders",        "name": "Builders" },
    { "id": "codev.backlog",         "name": "Backlog" },
    { "id": "codev.pullRequests",    "name": "Pull Requests" },
    { "id": "codev.recentlyClosed",  "name": "Recently Closed" },
    { "id": "codev.team",            "name": "Team", "when": "codev.teamEnabled" },
    { "id": "codev.status",          "name": "Status" }
  ]
}

Why this order reads better

Active triage flow is Builders → Backlog: glance at what's in flight, then look at what's next to start. Putting Backlog directly under Builders pairs the two surfaces that get checked together. Pull Requests is a downstream / completion-side surface — it makes more sense alongside Recently Closed at the bottom of the column. The new order tells a cleaner story top-to-bottom: workspace context → in-flight work → upcoming work → shipped/closing work → team/status meta-info.

Acceptance

• packages/vscode/package.json updated with the new order shown above.
• Fresh installs (or users who haven't manually reordered views) see Backlog above Pull Requests.
• Users who have already dragged views into their own order via the sidebar context menu keep their custom order — VSCode persists user-reordered views per-workspace and the contribution-declared order only applies until first user-drag.
• No other behavior change — views themselves are untouched.

Out of scope

• Renaming, splitting, or merging any view.
• Conditional visibility changes (no when clause edits).
• Bottom-panel migrations (vscode: introduce a Codev panel tab (bottom-area view container) to relieve sidebar overload #812/vscode: migrate Recently Closed view from sidebar to Codev panel tab #813/vscode: migrate Team view from sidebar to Codev panel tab #814/vscode: migrate Status view from sidebar to Codev panel tab #815/vscode: Codev Dev surface — bottom-panel tab with title-bar Stop/Restart, paired with always-visible status-bar chip #921 already track those).

Why BUGFIX

One-line array reorder in package.json. No design ambiguity, no logic change, ~5 LOC including the diff context. Single consult at the PR is the right amount of review.

[amrmelsayed]

On it! Working on this with the PIR protocol (plan + dev-approval gates before PR).