I think that:

1. TransitionsConfigArray complicated our types
2. it also complicated our implementation and slowed down the most basic scenario (we were searching for candidates with explicit descriptors in the array instead of just looking it up in a map)
3. it's rarely used feature (if used at all)
4. its existence it makes vizualization harder/less obvious. We don't visually order (nor denote order) anyhow. By removing the ability to order transitions arbitrarily in an array we make it more intuitive to interpret the visualization: explicit descriptions > longest-to-shortest partial descriptors > wildcard

This PR is not meant to refactor all inner bits. The main goal here was to remove this from the types and the public API, the internals could still use some further cleanups but that can be done at any time.