Try out a basic Backbone.Router example, adding a second (throwaway) view for switching between.
Refactor our views/routing away from test, towards the original flickr-browser purpose.

* Capture a route param for photoid, fake an object for now
* Remove test logging, or it will build up and destroy everything
One off formatting clean up, mostly for consistancy and readability
Add a basic photo model, start adding to the template, using inline sample data (we'll be replacing this with move live data soon)
Add a collection for Photos, filled with a single photo fixture. Use the collection to populate the PhotoView, which needs to call model.attributes now it's passed a Model rather than a js object
Move our sample data our of the router/view setup and in to it's own, non AMD, file.

* The file is in a git ignored dir, as we don't want real, personal, data in version control.
* I might add a sample file to illustrate the format, once it settles down, but it's reasonably clear what is expected from the code reading it.

* It's non-AMD as I want to keep the export format as simple as possible for other uses.
* Setting a global var is easy for other clients and we can use non-AMD shim to load it with require

* I'm not keen on the data-transformation going on in the router, it should move to a data access module soon, but for now i wanted to keep this commit small