Fixed -Wcast-qual gcc warnings

But they look a bit different.

warning: cast discards ‘__attribute__((const))’ qualifier from pointer target type [-Wcast-qual]
FYI, "-Wcast-qual" is not a default option.
The main idea: If some function receives "const void*"
why should it operate with "void*" (or something) afterwards (after casting)?

Fixed script unit tests. Fixed generate_test_runner configuration loadin...
(Thanks Mark McCrum. You are awesome!)

Awesome. Thanks so much!

- Modified rakefile to look in correct directory for script unit tests
- Updated paths in script unit tests
- Updated 'expectdata' files to match latest version of generated code
- Fixed bug which prevented generate_test_runner from loading config from
yaml file.

reworked character strings to be an array type so that storage classes are handled better for picky compilers.

- made help more clear
- added ability to rename setUp / tearDown / and test prefix.

support tests named spec as well.
clean up UnityBegin to make us not have to dig inside it to inject the filename.
Add UNITY_OUTPUT_START() and UNITY_OUTPUT_COMPLETE() for future use.

Added more robust handling of test includes, and to provide backwards API compatibility for Ceedling

rearranged project to centralize all self-test stuff under test directory. only pull in includes when required.

Removed Gemfile and Gemfile lock, since no longer requires test-unit, and we will assume the user has some version of Rake if they want to run the tests.

redirect UNITY_POINTER_WIDTH to define at last catchable moment. Update older gcc targets to be fully explicit.

Fixed posix default foregroud color to use 39/default instead of 37/light-gray, since was very hard to see on some dark background terminals.
Added Gemfile.lock for rubygems bundle environment consistency.

- rename the custom FLOAT_TRAIT type because the old name was poor

added macros for IS_DETERMINATE and IS_NOT_DETERMINATE

- rework to not bother with any of the ever-changing test frameworks in Ruby (sigh) for self-testing
- started working on cleaner floating point support. more coming.

* Add UNITY_BEGIN and UNITY_END macros to simplify usage
* Improve RUN_TEST to make line_num optional where possible

There was no reason that CMock init and destroy calls should be in the protected blocks. teardown is more flexible if verify is called afterwards.