docs($resource): note methods list is non-exhaustive

The existing documentation for custom action methods implies that only a small
list of upper case methods can be used for custom $resource actions.
perf($parse): don't use reflective calls in generated functions

Chrome and FF are smart enough to notice that the key is is a string literal, so this change doesn't
make a difference there. Safari gets a boost. I haven't tested IE, but it can't cause harm there. :)

http://jsperf.com/fn-dereferencing
feat($q): add streamlined ES6-style interface for using $q

This potentially helps lead the way towards a more performant fly-weight implementation, as discussed
earlier in the year. Using a constructor means we can put things in the prototype chain, and essentially
treat $q as a Promise class, and reuse methods as appropriate.

Short of that, I feel this style is slightly more convenient and streamlined, compared with the older
API.
WIP make Q more bloobirdy
WIP subset of Bluebird functionality / implementation

Things remaining:

1. Make this compatible with the original $q implementation

2. Sort out the error logging story (make use of Bluebird's machinery for this + $exceptionHandler by default)

3. Remove more bits that aren't needed for Angular.
WIP bluebird
WIP add promises-aplus-test-adapter-prefix.js
MORE WIP
WIP fix $compile tests