Starting a context object where we allocate memory and the app works on things.

[rcthomas]

This PR starts a context object for the app.

• Include guards.
• Enforce removal of newlines after return type and function decl and def. Deviation from KR: I think blank lines after opening brace and before closing brace in function definition is okay.
• Allowing space before ifdef esp for end include guard, another K&R deviation apparently.
• Taking out the garbage.c
• Using clang here, added context objects and -W flags. Any uncrustify stuff also should be cleaned up.
• Moved single-use init functions into the main init part, removed the output bit since this type just holds some data for a little bit. Also shortened variable names since we are being 80 columns.
• Type typo.
• Now has context in it.
• App context, where things are allocated and live mostly, and objects are worked on by the app.

[rcthomas]

Unless you're really excited about the prospect I would not condone option 2! From my perspective a number of these commits are perfunctory, so I didn't really worry about making sure they were separate commits. For instance the little adjustments I made to uncrustify.cfg, compiler flag stuff, were pretty tiny and uncontroversial (IMO) and are much less important than the new source files. The variable renames are something that should be called out clearly though.

Go ahead and update the dev docs.