Fix enabled feature drift for latest upstream DMG

[joshyorko]

What changed

• retarget the API-key service-tier model and fallback descriptors to the current 26.707.72221 webview bundles
• retarget project task sorting to the current page-* asset
• update the current sort-state markers used to fail closed on upstream drift
• remove the superseded bundle shapes instead of retaining compatibility fallbacks

Why

The current pinned upstream DMG built successfully but acceptance rejected promotion because the enabled api-key-service-tier and project-task-sort patches could not find their owning assets.

User impact

Users with these optional features enabled can rebuild and promote the current DMG without dropping either feature.

Source-of-truth files

• linux-features/api-key-service-tier/patch.js
• linux-features/project-task-sort/patch.js
• adjacent feature tests

Validation

• node --test linux-features/api-key-service-tier/test.js linux-features/project-task-sort/test.js
• the repaired fork integration was rebuilt against DMG 40e34814e74e30943c209ebd4da94cd4de3581a52c5bffbe2bcf2e488d6361c6 with the saved 24-feature profile
• acceptance changed from three enabled-feature blockers to accepted; these features reported 3 applied patches and 1 applied patch respectively

Additional review and isolated acceptance confirmation are still in progress; this PR intentionally remains draft.

[joshyorko]

I have this PR under additional review with Sol using extra-high reasoning, and validation/testing is still in progress. Please do not review, modify, merge, or otherwise act on it while it remains in draft. I will mark it ready when that review and testing are complete.

[ilysenko]

this clearly calls for Ultra. 😄