feat!: standardize id generation

[bowheart]

@affects atoms, react, stores

Description

As we've added features to Zedux, different id types have cropped up all over the codebase. These ids are all different shapes and aren't customizable. We can do better.

Rework ecosystem.hash and replace the id generator with ecosystem.makeId. Add a makeId ecosystem config option for easily customizing id generation.

Standardize id shapes.

• React components: ComponentName-:idFromUseId: -> @component(ComponentName)-:idFromUseId:
• Selectors: @@selector-name-randomId-paramsHash -> @selector(name)-consistentId-paramsHash
• injectMemo selectors: injectMemo(injectingAtomId)--randomId -> @memo(injectingAtomId)-consistentId
• Standalone signals: @signal-randomId -> @signal()-consistentId
• Injected signals and mapped signals: @signal(injectingAtomId)-randomId -> @signal(injectingAtomId)-consistentId
• Listener nodes: no-randomId -> @listener(listenedNodeId)-consistentId

Additionally, when component, selector, or hashed function/class reference names are unknown, they all use the string unknown instead of rc-, unnamed, anonFn, or UnknownClass respectively.

Atom ids are unchanged, mostly because that would be a bigger change than all these other id changes combined. Atom ids are used for hydration, snapshotting, and restoring state. Leaving them as-is is fine. They can be easily customized (e.g. to match other ids with an @atom(templateKey)- prefix) with the new makeId ecosystem config option if desired.

This PR removes the IdGenerator class as per the v2 spec.

Breaking Changes

ecosystem._idGenerator is gone, replaced with ecosystem.makeId.

Ids all generate differently. See the v2 migration guide (after this PR merges) for an example makeId implementation to get the old ids back.