Some minor changes for parse_output.rb (Thanks @farrrb  and @jeremyhannon !)

MISRA 19.10: surround each macro param with parens.

MISRA 2004 rule 19.10: inside macros, surround each parameter usage with parentheses.

MISRA - param names match; macro params in parens

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

- String split now works correctly for windows and unix (cross platform)
- Removed unnecessary whitespaces in the xml output (beautifies the output)
- Added support for TEST_IGNORE() (without message)

Added more detail on test naming.

Fix unsigned integer underflow in UnityAssertEqualIntArray (Thanks @shreyasbharath )

Test runner generation: Wrap setjmp.h inclusion in ifdefs. (Thanks @flowher !)

Auto generated test runner should generate a code  which includes
setjmp.h only if UNITY_EXCLUDE_SETJMP_H is not defined

Allow suiteSetUp() and suiteTearDown() to be provided as normal C functions (Thanks @jlindgren90 )

Fix missing TEST_ASSERT_EACH_EQUAL_HEX_MESSAGE -- Thanks @codehearts !

Color test results using ANSI escape codes (Thanks for the work, @VLambret !)

Help error detection by adding specific colors for test results. This
behavior is activated only when unity if compiled with UNITY_COLOR flag.

Bugfix greater/less than asserts with unsigned int. (Thanks @jsalling! I can't express what a GREAT job you did with this.)

- Enable support for Green Hills Software compiler
- Define weak implementations only once except on Windows

MinGW supports a limited form of weak symbols, with the restriction
that weak/default implementations need to be defined in the same
translation unit they are called from.  Strong/overriding symbols
may of course be specified in a different translation unit.

 Make all comparison operators on integers available

 Check for unsigned types, add 'or equal to' support
 Consolidate to one function to remove repeated code

This is simpler and more flexible than embedding C code in the Ruby options
(:suite_setup and :suite_teardown).  However, support for :suite_setup and
:suite_teardown is kept for backwards compatibility.

Several configurations are possible:
1. :suite_setup and :suite_teardown options provided and used.
2. :suite_setup and :suite_teardown options not provided (nil):
  2a. Weak symbols not supported; suiteSetUp() and suiteTearDown() are not called.
      It would be simpler to make user-provided functions mandatory in this case,
      but it could break some pre-existing test suites.
  2b. Weak symbols are supported and the stub implementations of suiteSetUp() and
      suiteTearDown() are called if there are no user-provided functions.
  2c. Weak symbols are supported but overridden by user-provided suiteSetUp() and
      suiteTearDown() functions.

Fix compiler warning due to reusing symbol 'exp'.

Cleanup Greater than and Less than asserts from other PR (#264) (Thanks @dpostorivo and @Dommar92 !)