feat: Independent color settings per background type

[Copilot]

Background types (solid, gradient, geopattern) previously shared color state. Changing gradient colors would overwrite the solid color when switching back.

Changes

Data Model

• Added typeColors object storing per-type color state:

  typeColors: {
    solid: { color: '#FF0000' },
    gradient: { color: '#0000FF', secondaryColor: '#00FF00', gradientDirection: 'to right' },
    geopattern: { color: '#F8F6F1' }
  }

State Management (useBackgroundPreferences.js)

• Migration logic for existing preferences (preserves current colors)
• updatePreference() now writes to type-specific path when updating color, secondaryColor, or gradientDirection
• getBackgroundStyle() reads from active type's color settings
• Maintains global fields for backward compatibility

UI (BackgroundSettings.jsx)

• Color inputs bound to current type's values
• Gradient-specific properties only update when type is gradient

Tests

• Added verification that solid→gradient→solid color transitions preserve independent state
• Updated existing tests for new data structure

Behavior

// Set solid to red
updatePreference('type', 'solid')
updatePreference('color', '#FF0000')

// Set gradient to blue→green
updatePreference('type', 'gradient')
updatePreference('color', '#0000FF')
updatePreference('secondaryColor', '#00FF00')

// Switch back
updatePreference('type', 'solid')
// Color is still #FF0000 (not #0000FF)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>feat: More granular settings</issue_title>
<issue_description># Feature Request

Describe the Feature Request

I'd like all the different settings for the background to be individual, rather than share the colors between them.

Describe Preferred Solution

If i change the color in the gradient, it should not affect the solid color view.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes feat: More granular settings #470

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Test Results - JVM

946 tests   938 ✅  1m 7s ⏱️
 76 suites    8 💤
 49 files      0 ❌

Results for commit 9808f0e.

[github-actions]

Test Results - Native

946 tests   938 ✅  1m 8s ⏱️
 76 suites    8 💤
 49 files      0 ❌

Results for commit 9808f0e.

[github-actions]

Pull Request closed and locked due to lack of activity.
If you'd like to build on this closed PR, you can clone it using this method: https://stackoverflow.com/a/14969986
Then open a new PR, referencing this closed PR in your message.