Fix working directory when calling make

Due to a recent change in TextMate.executor it would always change the working directory to the project directory, which would fail if TM_MAKE_FILE was set to build/Makefile (and that file used relative paths).
Use version 1.8 of ruby for bundle items

10.7 and 10.8 only include ruby 1.8, so all bundle items have been written to work with that. Optionally supporting ruby 1.9 and 2.0 is problematic as these versions are not fully backwards compatible.

#ignore
Do a better job at locating Makefile

We now search from current file’s directory and up to the project directory, if TM_MAKE_FILE is unset, and there is no Makefile in the project folder.

Also show better error when no Makefile is found.
Use true for the disableIndentCorrections value

#ignore
Change to Makefile directory when “Build Target…” calls ‘make’

This is when calling ‘make’ to obtain phony targets. Previously it would fail to resolve relative includes, which manifested itself by an error following the build output, in addition to not listing potential targets from these included make files.
Point to ruby 1.8 shim

Using a shim allows us to catch when 1.8 of ruby is not present and provide other options.

#ignore