feat!: improve findAll, ions, and clean up types, properties, and deprecations

[bowheart]

@affects atoms, stores

Description

There are just a few last things to round up for Zedux v2. Knock them all out.

Add an array overload to ecosystem.findAll that's a shorthand for .findAll({ include: [...mySearchList] }). This is especially useful now that all node types can be returned.

Add a type overload to ecosystem.findAll so editors autocomplete with the new @-prefixed strings by default. This gives some very sleek DX - type ecosystem.findAll(' and you'll see @atom as the first suggestion, which should be the most common. Same goes for the new array overload.

Deprecate the old store-based AtomInstance .setState function property. Prefer .set instead - it does the same thing for store-based atoms, but will make it easier to migrate to signals-based atoms.

Remove the implementation of useAtomSelector. Make it an alias for useAtomValue which now fully supports selectors.

Breaking Changes

Signals-based ions (created via the @zedux/atoms or @zedux/react package's ion factory) now set ttl to zero by default. This was something we almost did years ago with the original spec. I wasn't sure if it was a good default at the time. Now I'm sure. And with the new signals-based ion factory being completely distinct from the old store-based ions, we get a free opportunity to reset. So do it.

The atomDefaults ecosystem config option is gone. The only supported default was ttl and the only other default that made sense was 0. That should no longer be useful since ions are now a built-in way to create ttl: 0 atoms.

The AtomSelectorOrConfig type is renamed to SelectorTemplate.

Stop preventing external nodes (components and event listeners) from being returned by ecosystem.findAll. I've been caught off guard by that behavior multiple times already. So it's bad. ecosystem.findAll can now return every node in the ecosystem.

Rework the AtomInstance _infusedSetter and _set properties to a new x property (short for exportsInfusedSetter). Users shouldn't be using that directly, so obfuscate it. Make it a single getter property that overwrites itself when first used.