register/subscribe decorators support different URI syntax from what session.register and session.subscribe support

I'm not sure how this happened but it seems like the pattern-based URI syntax supported by the register/subscribe decorators and the underlying Pattern object that supports them is not actually supported by the register/subscribe methods on the ApplicationSession class.

Example:

@wamp.register('a.b.c.<something>.e.f', options=RegisterOptions(match='wildcard', details_arg='details'))
def my_endpoint(details):
    pass

You would expect to be able to call that using:

session.call('a.b.c.blahblahblah.e.f')

but doing so will yield a No Callee error.

However:

session.call('a.b.c.<something>.e.f')

works when it probably shouldn't.

Additionally:

@wamp.register('a.b.c..e.f', options=RegisterOptions(match='wildcard', details_arg='details'))

raises an exception

It seems like the support for this is only half-implemented at the moment or did some commits get lost in the woodwork?

Start by comparing the register/subscribe decorators and their Pattern object with the register/subscribe methods on ApplicationSession, using the URI examples in the issue to reproduce each discrepancy. Done means the supported pattern syntax behaves consistently across decorators and session methods, including the wildcard call and the invalid double-dot pattern.