Client and server same path example

Show example for having a client and server route controller for the same path. I'm using this in production now to avoid using the `spiderable` package and it's working quite well.
bump version to 1.0.0-pre4
move helpers.js to client and server and fix urlFor, pathFor to...

... allow passing dynamic path values directly in the options like this:

{{urlFor route='someroute' _id=someid}}
oops, add the helpers.js file
Update README.md
Added note about 0.9 docs
Create Contributing.md
Update Contributing.md
Mention server-side routes for implementing REST endpoints
Update README.md

Make it clearer what's going on
Chris couldn’t make up his mind :) #919
Fixed breaking test
Default template name converter to nothing. Fixes #922
Fixes #924
Allow static data Fixes #929
Better error for missing hooks. Fixes #930
Fixed problem where loading hook wasn’t used. #921
fix optional and regular expression paths

fixes #912 and #934.
do not create new route controllers if the route is the same...

See Issue #895.

Key use case: Be able to build an Asana like interface where you want
the url to change to the item that is selected but you don't want to
rerun all helpers (thereby re-rendering the entire task list every
single time you click on something).

Couple of changes here:

1. On dispatching a new url, if the route is new then create a new
controller as we've always done before.

2. If the route is the same as the previous route AND we already have a
controller, just reconfigure the controller with the new url and
dispatch context. Don't create a new controller instance. This means we
don't need to rerun all helpers, since the controller hasn't changed.

3. Add getParams and setParams methods to controller to reactively get
and set the parameters. This way, if a helper needs to respond to
parameters reactively it can use this.getParams(). this.params will
still work the way it did before.

4. Add this.location = Iron.Location so that folks can reactively get
the current location from Iron.Location which will be reactive.

5. Instead of having iron:middleware-stack set the parameters, we'll do
it once from the router.

TODO:
- Update iron:dynamic-template to create dependencies for helper lookup.
- Update Guide and changelog getParams
- I got rid of use(...) for now to simplify things. Need to plug onRun
  into the middleware stack. Will probably do the same thing with
  onAfterAction. Show examples of how to use Connect middleware with the
  existing hooks. Will revisit how to mount handlers at paths.
oops fix bug in route controller default action path