Add missing autoload include for console components page

And better explain where files should be placed in order to be auto-loaded.
@WouterJ Very nice breakdown - I couldn't have thought of it better! And I agree that we have all 3 audiences and also that we don't need to teach people how to bootstrap a project, structure things or use Composer.

So, where does that leave us? I think:

A) We show a require of the `autoload.php` at the very top of every component docs in the installation section. I'm basing this off of Guzzle, which is a library that a lot of people use: http://guzzle.readthedocs.org/en/latest/overview.html#installation

B) We include a patch like this one for the rare case where we're assuming you have some auto-loading setup. We do this in the installation section.

For the 3 groups:

1) Full-stack FW users will not (hopefully) bother with the installation. So they hit no new problems
2) People wanting to include this in their non-FW project will have the autoloader and autoloading details *if* they need them.
3) People wanting to learn more about the internals will skip past installation as well.

Cheers!