Allows specifying the namespace and the capitalize params

[fedefernandez]

Relates to #599

This can be considered the first step where we allow to specify a namespace and the ability to capitalize the gRPC method

[codecov]

Codecov Report

Merging #601 into master will increase coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #601     +/-   ##
=========================================
+ Coverage   82.36%   82.46%   +0.1%     
=========================================
  Files          62       62             
  Lines         964      964             
  Branches       12       12             
=========================================
+ Hits          794      795      +1     
+ Misses        170      169      -1

Impacted Files	Coverage Δ
...igherkindness/mu/rpc/internal/server/package.scala	100% <0%> (+8.33%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 76afadd...48fef20. Read the comment docs.

[rafaparadela]

It's great to provide flexibility to define customized protocols through the @service annotation.

I have seen that your tests are proving that both MethodName and Namespace operate perfectly separately, but given that we are transforming the name of the service by capitalizing and concatenating the namespace, I would suggest to prove that both transformations interoperate as we expect.

Beside this minor (non-blocking) suggestion, this implementations looks great to me.

[fedefernandez]

Thanks @rafaparadela. The namespace is for the service and the Capitalize option is for the method, so I prefer to have those separated in the annotation. I'll provide only one setting key at plugin level, because as you said they are related.