REST: Allow multipart RESTName

[ddworak]

Consider:

@REST
trait Api {
  @RESTName("auth") def auth: AuthApi

  @RESTName("app/v3") def secure(token: Token): SecureApi
}

This is currently impossible due to URLEncoder.encode on all RESTNames and AFAIK requires nesting the interface.

[ddworak]

@ghik: issue to be closed with #225, right?

[ghik]

Yes, new REST framework lets you specify arbitrary path fragments, including empty ones and also supports intermixing path parameters with fixed path fragments.