refactor: simplify forcing update

[amirhhashemi]

I'm not exactly sure if it's any better in terms of performance but I think this is a simpler approach. It has two benefits that I can think of:

1. It doesn't create a new array every time a transaction happens.
2. Equality check is not needed: Every time setSignal gets called, Solid runs oldValue === newValue to check if the value is actually changed. With this approach this check is not needed.

https://www.solidjs.com/docs/latest/api#options

[lxsmnsyc]

I think forceUpdate can still be kept. I'm not sure if the transaction event passes a value but if it does, it's unideal to be kept in memory (by writing it into a signal), so it's better to do a 0-arity function like forceUpdate, but sure, that equals option should be better

[amirhhashemi]

Good point, I fixed it.

[lxsmnsyc]

Thanks!