Don't report an error when cleaning missing files

When doing a `rake clean` or `rake clobber`, it is often the case that
some of the files don't exist.  The desired end state of the clean or
clobber task is that the specified files no longer be present at the
end of the task; if they weren't there in the first place, the
post-condition is still satisfied.

Without this change, running a `rake clean` or `rake clobber` is too
noisy, and yet silently failing to delete a file is not a good
solution either.

This may not be the best fix for this.  I tried two options:

1) Add a second rescue block for `Errno::ENOENT`.  This fails
`test_cleanup` in JRuby, because JRuby raises `Errno::ENOENT` for that
case.

2) Use `File.exist?` as I've done.  In order to make this work, I had
to modify the permissions used in `create_undeletable_file`, because
`File.exist?` returns false for a file in an unreadable directory.

With either of these solutions, there are corner cases where one or
more Ruby implementations will silently fail to delete a file.  My
opinion is that those corner cases are rare enough that this PR makes
sense for the far more common case.
Be smarter about determining whether the file is already gone

Per @drbrain's suggestion, this version only prints the failure
message if the file exists or if it has an unreadable or unexecutable
parent directory.
Use `private_class_method` instead of private
fix typo in comment
Merge pull request #267 from Elffers/master

fix typo in comment
Merge pull request #266 from randycoulman/clean-missing-files

Don't report an error when cleaning missing files
Add #267 to History
Add #266 to History
Read stderr from cpu count command to avoid hang

Leaving stderr unread causes hangs.  I don't remember why, though, the
documentation somewhere probably says.

See #268
Set release version and date
Set release version to 10.3 due to new features
Lookup prerequisites with same name outside of scope instead of matching self