rfc3: require request/response topic strings to follow service.endpoint form

[garlick]

Problem: RFC 3 states that topic strings in request messages MAY include period delimiters", but for RPCs we have a convention of service.method that should be followed.

Since Flux services have implicit methods like disconnect, it probably makes sense to require there to be a distinct service and method component in request/response topic strings.