Fix docs.

- fixed ANSI (C89) issues, including #418

Fix compiler complaint about declaration after statement

The realloc was not taking in account extra bytes needed for the the pointer proper alignment

Make sure the malloc alignment is always aligned to the architecture's pointer size

parameter names should match between declaration and definition.
(MISRA 2004 rule 16.4)

- Fixed some style issues.

Starting to enforce our coding style. The first step is that we’ve pulled in Rubocop to check out Ruby syntax. There is likely a bit of customization to do yet AND there is definitely that backlog of todo’s that we just told it to ignore.

Used clang-format, which produces noise on stuff you don't care about
and requires setting it up to match the existing code base. Kept the
potentially useful changes, discarded the rest, some manual tweaking
required. It did catch lots of pesky indentation mistakes.

Remove UNITY_FIXTURES option, which was probably not doing what was
originally indended. It was suppressing the test name even in quiet mode.

Revised internal type naming scheme to better sandbox Unity away from everything else. Sure, short was nice, but not at the expense of naming collisions.

Mangling issues, as always.

 Remove stdint.h from the C89 build due to -pedantic warnings from type
  'long long' and constants like UINTPTR_MAX = 18446744073709551615ULL

 Make it more clear that each test of the internal heap implementation
  should free in LIFO order. Without this check, memory can be stranded
  but still pass.

 The internal malloc must free in LIFO order

 This reverts commit 783fcaea
 The guard memory bytes should never be freed inside unity_malloc()

I believe if realloc() returns a pointer to a different location, the old location is freed. However, the pointer 'n1' is not freed if realloc fails to obtain a large enough block of memory and returns NULL. (more details on [StackOverflow](http://stackoverflow.com/a/16676964)).