Split passes into different categories

Currently, there are 57 _passes_ that are available in Binaryen. With this pile of _passes_, it's difficult to decide what _passes_ should be used for some general yet specific task (e.g reduce the size or speed up the execution). There is an idea to split it into multiple categories for each _passes_. Some categories that I can think of are:

- [ ] optimization related to speed up the execution
- [ ] optimization related to reducing the binary size
- [ ] passes which produce something that can help the debug process

I have done some [initial work](https://gist.github.com/DrSensor/5cdbbc02fa7d57015913df28b3f2021a) by trying some passes if it shrinks the size using this [example](https://github.com/DrSensor/example-vue-component-rust). Still not sure if it's correct.

Review the repository's existing Binaryen pass handling, then compare it with the linked initial experiments and example project. Determine whether the proposed speed, size, and debugging categories are complete and well-defined. Done means the categories and pass assignments have an agreed scope and are implemented consistently.

Written by the indexing model from the issue text.