fix(web): save Timeline/board filters per user by default (PE-1)

[prakruthi2411]

Summary

Implements PE-1 — PACA Timeline Board Filters Should Be Saved Per User.

• View settings already persist in a per-user override (PUT …/views/:id/config)
• The primary save action for people with views.write is now Save only for me, so filters no longer publish to the whole team by accident
• Save for everyone remains in the dropdown for the team default
• E2E specs/feature files updated to match the new footer

Test plan

• Open Timeline (or Product Backlog) view settings as an Admin/Editor
• Change a filter or Sort by → primary button is Save only for me
• Save, then reopen the board as the same user → filters are restored
• Open the same board as another user → they still see the team default
• Dropdown still offers Save for everyone, and that updates the shared view
• A Viewer still sees a single Save button (personal only)

Made with Cursor

[pullfrog]

ℹ️ Minor suggestions only — one doc/spec consistency nit.

Reviewed changes

• Footer action swap (view-settings-panel.tsx): for views.write holders the split button's primary action is now handleSave ("Save only for me", gated on differsFromEffective), and the dropdown now offers handleSaveForEveryone ("Save for everyone", gated on differsFromShared). Viewers still get the single plain "Save". This is an exact swap of the two existing actions — handlers, gates, and the persistence paths are otherwise untouched.
• e2e specs: view-settings.spec.ts reorders the locator helpers (saveOnlyForMeButton is primary; saveDropdownTrigger is now its following sibling) and saveForEveryoneAndWaitClosed opens the dropdown first; interaction-views.spec.ts admin save tests now drive "Save only for me".
• Gherkin features: view-settings.feature and view-settings-fields.feature prose updated to describe personal-first saving.

ℹ️ Nitpicks

• view-settings-fields.feature now says the field scenarios' "the user saves the view settings" means "Save only for me", but the field-picker tests that actually save still use saveForEveryoneAndWaitClosed and assert the shared config (view-settings.spec.ts:716, :737, :756 — e.g. expect(view.shared_config.fields).toContain("due_date")). Align the prose with the tests, or move those tests onto the new primary save, so the feature file and its spec agree.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}

[pikann]

LGTM! Thank you for the contribution! 🚀