Re-write `exit-codes.mdx` into an article of the Book

[novusnota]

Great tact-fireworks may suit as a starting point. Furthermore, the Fireworks contract should be split into many smaller contracts (or receive() functions) to showcase one error and exit code per one transaction, as suggested by @anton-trunov.

Additional things to fix:

• Table of Contents for every exit code through headers
• Disallow LaTeX numbers in headers for better search
• Grammar, spelling, punctuation
• Add missing exit codes, i.e. exit code 11 is not documented, and there are others!

Additional links:

• Writing Tests Examples
• Fireworks in FunC
• Description of exit codes thrown in Fireworks
• Exit Codes page in Tact docs
• Extra exit codes of Tact
• Exit codes of TVM

Also — describe what "cannot be faked" means for exit code -14, see: https://github.com/ton-blockchain/ton/blob/20758d6bdd0c1327091287e8a620f660d1a9f4da/crypto/vm/vm.cpp#L492.

Also, describe what they are in general and how they occur.

Related issue: #101

[anton-trunov]

Tact generates exit codes for require depending on the concrete error message string and thus the exit codes can be arbitrary