Use llvm::outs for jit.dump machine code

The jit.dump used std::cout previously.  This could cause a problem
when using jit.dump=7 because llvm::outs() for IR and std::cout
for machine code could conflict and the machine code dump could get lost
Add spec for ancestors on a singleton class

MRI 1.9 did not include the singleton classes in the list of ancestors
but 2.x does.
Merge pull request #3036 from southerngs/llvm_out_machine_code

Use llvm::outs for jit.dump machine code
Removed cruft from configure refactor.
Removed config.rb.in from packaged files.
Use explicit vendor/cache for packaging.
Updated Changelog.
Bumped version to 2.2.7.
Reset release date.
Update singleton ancestor chain

MRI 1.9 did not include BasicObject's singleton class in the ancestors
of a singleton class. 2.x introduced this, so let's match it.
Fixed build revision in tarballs.
Added comment to env dependent spec.
Force CI env to UTF-8.
Unexplode CI env matrix.
May all the OSX builds be merry and green forever.
Update instructions & rubinius version num: 2.2.7
Fixed checking bootstrap, runtime gems.
Merge pull request #3039 from asveepay/debianize_2.2.7

Update instructions & rubinius version num: 2.2.7
Ignore build_ruby/build_signature.
Failing spec for String#delete with multibytes.

It looks like the current implementation of String#delete! iterates over bytes
instead of characters. Oddly enough this seems to work for Japanese Kanji but
not for other multibyte sequences.

See #3019.