Proposal: Centralize definition of OPs into a single file

Users must read or touch many files to reason about or define a new OP. Currently that list includes the tele_ops table, the Ragel parser, the module, test, and simulator Makefiles, the help mode documentation, and the paper documentation.

We're already doing a little bit of codegen to create op_enums.h, but lots of this other material could be generated also.

The ideal would be a single file that describes all the information for an OP or small collection of related OPs, so adding or altering behavior could target a single location in the source tree. If a single file was untenable, then two separate files for definition and implementation in the same folder would also be an improvement.

In addition to making adding OPs easier, this change would also make it easier to refactor the way OPs are processed and documented, because all the implementations could be changed by changing the codegen.

Start by mapping the tele_ops table, Ragel parser, module, test, and simulator Makefiles, help documentation, paper documentation, and existing op_enums.h generation. Determine whether one definition file or separate definition and implementation files can cover these sources. Done means OP information has a clearly defined central source and the affected code, tests, simulator, and documentation are generated or updated from it.