fix: Addresses overeager 'there are unsaved changes' dialog in settings

[brunobergher]

Description

Up to now, the "Done" button in settings would always warn about unsaved changes, even when there weren't any.
This fixes the behavior of one of the panels, which was flipping a dirty bit unnecessarily.

Test Procedure

There are automated tests, but to manually check it:

1. Go to settings
2. Click done – you should get no popup
3. Go back to settings
4. Change something
5. Click done – you should get a popup

---

Important

Fixes overeager unsaved changes dialog in settings by refining change detection logic in SettingsView.tsx and ApiOptions.tsx.

• Behavior:
  • Fixes overeager unsaved changes dialog in SettingsView.tsx by refining change detection logic.
  • Adjusts setApiConfigurationField in ApiOptions.tsx to pass false for non-user actions.
• Tests:
  • Adds SettingsView.change-detection.spec.tsx to test change detection logic.
  • Adds SettingsView.unsaved-changes.spec.tsx to verify unsaved changes dialog behavior.
• Misc:
  • Updates setCachedState logic in SettingsView.tsx to prevent unnecessary change detection.

^{This description was created by for 4e54cf9. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Nice improvement: treating undefined, null, and empty string as uninitialized prevents false change detection. Consider extracting this check into a helper for reuse and clarity.

^{This comment was generated because it violated a code review rule: irule_tTqpIuNs8DV0QFGj.}

[roomote]

I found some issues that need attention. See inline comments for details.

[roomote]

[P2] Internal sync path correctly marks isUserAction=false. To avoid future drift, audit similar internal sync sites (provider/model defaults, migrations) and consider centralizing via a small helper to ensure they always pass false.

[roomote]

[P3] The isInitialSync detection is duplicated logic you’ll likely want consistent across fields. Consider extracting a small helper (e.g., isInitializingValue(prev, next, isUserAction)) and unit-testing it so future edits don’t regress this behavior.