Swap the order of the two derived store signatures to fix TS inference

[AlexGalays]

Before

• Using derived(store, (value, set) => {}) fails to infer the parameters of the second function (it infers them as any which seems to indicate it picked the simpler signature where the function only has one parameter)
• All other forms compile fine, even the one with the set param and a start value.

After

• All combinations compile and infer properly.

I just swapped the order of the two declarations, now forcing TS to consider the more complex signature first.

PS: Have you considered progressively rewriting the tests in typescript to catch these kinds of issues?

Cheers

[Conduitry]

Released in 3.32.1, thanks!