Attribute on parent routes can confusingly break parsing

[parsonsmatt]

You can put attributes on parent routes:

/foo FooR !some-attribute:
    / FooIndexR POST

But if you put the : immediately after the route name, then the parsing becomes Very Weird. It will pass parsing! But it will - instead of nesting FooIndexR under FooR - it will just make FooR a top-level route.

/foo FooR: !some-attribute
    / FooIndexR POST

becomes [ResourceLeaf ("/foo" resource for FooR), ResourceLeaf ("/" resource FooIndexR)]

The parser should support attributes before and after the : - before for backwards compatibility, and after because that's how all the other ones work.