Deployment set scope on route

[chriskapp]

To access a protected route a user must assign the route to a specific scope. At the moment this must be done manually after deployment. We should add a scope property to the route i.e.:

version: 1
scope: ["foo", "bar"]
methods:
  GET:
    public: true
    responses: 
      200: Todo-Collection
      500: Message
    action: "${dir.src}/Todo/collection.php"

If we deploy such a route we sould automatically create the scope foo and bar and assign the route. This would simplify setting up protected routes. Since a user could automatically obtain such a scope through OAuth2.

Also it would be possible to provide a tag input at the backend where a user could set these scopes per route.

[chriskapp]

Implemented in the 0.9.5 release