Documentation/process for adding new callbacks

[AndrewFasano]

It used to be fairly straightforward to add a new callback, for example:
95fb1a9. We would:

• Add to cb-defs.h enum + docs and signature
• Add 1-line macro to cb-support.c
• Execute the self-updating cb-support.h script and pypanda's create_datatypes.py scripts

Since merging #1105 this process has gotten a bit more complex and I couldn't find any documentation. I managed to successfully add a callback on a branch here (it doesn't do anything, but it builds)
ac62025. This issue can be a placeholder for documentation, but we should write some docs and/or remove all the unnecessary manual effort with the context-based headers!