Support before/after hooks on user remote RPCs

[renatoaf]

Currently, "before" / "after" hooks are invoked only on "sys" RPCs on remote.go module.

Therefore there's no way to add before/after hooks on "user" remote requests, only via handlers.

This MR invokes the existing hooks on remote pipeline with ExecuteBeforePipeline and ExecuteAfterPipeline.

[coveralls]

Pull Request Test Coverage Report for Build 6745955476

• 20 of 20 (100.0%) changed or added relevant lines in 1 file are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.05%) to 61.686%

---

Files with Coverage Reduction	New Missed Lines	%
modules/binary.go	2	73.91%

Totals
Change from base Build 6711890773:	0.05%
Covered Lines:	4838
Relevant Lines:	7843

---

💛 - Coveralls

[felipejfc]

I think we should create another set of hooks "remoteHooks" for Remotes as they're very different than Handlers.
Remotes -> General Server to Server RPC
Handlers -> Frontend to Backend RPC generated from a player handler call.

[renatoaf]

I considered doing that initially also to avoid introducing this behavior change unexpectedly, however I figured that every kind of RPC share the same "HandlerHooks" struct. For example "sys.push" and "sys.bindsession" already trigger the same set of HandlerHooks we have. Should be a small change, do you think it's worth doing the separation just for remotes?

[felipejfc]

I considered doing that initially also to avoid introducing this behavior change unexpectedly, however I figured that every kind of RPC share the same "HandlerHooks" struct. For example "sys.push" and "sys.bindsession" already trigger the same set of HandlerHooks we have. Should be a small change, do you think it's worth doing the separation just for remotes?

I believe it is, so that we reduce the probability of human error when creating these hooks. The separation will help with clarity of what will run when. Can you adjust the PR?

[renatoaf]

Closing this as the work was merged/finished on this new PR: #365