Reactive style bindings overwrite server-rendered styles during hydration #3180

Describe the bug

Reactive style bindings overwrite server-rendered styles during the
initial hydration pass.

This differs from reactive class and ordinary attributes, which preserve
the server DOM until the first reactive update.

Given this server-rendered element:

<div
  _hk="0"
  class="server"
  data-value="server"
  style="color: red"
></div>

and this client component:

const [value, setValue] = createSignal({
  token: "client",
  color: "blue"
});

const dispose = hydrate(
  () => (
    <div
      class={value().token}
      data-value={value().token}
      style={{ color: value().color }}
    />
  ),
  container
);

the DOM immediately after hydration contains:

div.className;         // "server"
div.dataset.value;     // "server"
div.style.color;       // "blue"

The class and data attribute preserve their server values, but the style
is immediately replaced with the client value.

Steps to Reproduce the Bug or Issue

1. Insert server markup with a dynamic inline style.
2. Hydrate it with a different initial client style value.
3. Inspect element.style immediately after hydrate().

Expected behavior

The server-rendered style should be preserved during initial hydration, consistent with class and other attributes. The first subsequent reactive update should apply the client value.

Platform

• @solidjs/web: 2.0.0-rc.4
• next: f051db6a
• Tested with both native and Babel compiler paths
• jsdom 25

Additional context

setAttribute, setProperty, setAttributeNS, and className return early
for hydrating nodes.

The style() and setStyleProperty() runtime helpers do not perform the
same hydration check, so all reactive style paths write to CSSOM during the
initial claim pass.

I searched the existing style and hydration issues and could not find one
covering this initial hydration behavior.