Apply ghastly hack to fix failing spec

This is evidently breaking all the rules about encapsulation and not
testing implementation details, but it's the quickest way to get this
failing test passing again.

(And note, it is not strictly worse than what was there before either,
because the reason the test was broken was precisely because it was
wedded to implementation details; it turns out that this spec is an
assertion about implementation details...)

Signed-off-by: Wincent Colaiuta <win@wincent.com>
Move RubyFileScanner specs into subdirectory

We had 4 remaining spec failures in this file; this commit tries to
stick as close to being a straight move as possible to make it clear
what's happening, but just moving the code makes the specs pass.

The issue is that we recently factored some of the functionality of the
FileScanner class into a RubyFileScanner subclass, so the specs for the
FileScanner were seeking to verify behavior which was no longer present
in the class.

In this commit we split the specs out just as we split the FileScanner
and RubyFileScanner functionality out. It moves the code into another
file and changes the references to the FileScanner class to
RubyFileScanner.

Signed-off-by: Wincent Colaiuta <win@wincent.com>
Fix controller spec failures

With "judicious" stubbing. The amount of stubbing in this spec is an
immense smell, but pursuing the quick fix in the name of getting the
suite green again rather than engaging in a deeper reworking for now.

Signed-off-by: Wincent Colaiuta <win@wincent.com>