Fix context passing in OWNER role resolver

[bajtos]

Description

With the move to explicit context passing of an options object, internal calls to find etc need to be updated to pass the necessary information along, too. In this case, isOwner calls findById on a Model, but does not pass an access token in options.

cc @DaGaMs@ebarault

Related issues

• findById does not include "options", but find does? #3209
• Inject remoting context to options arg #3023
• supersede fixed context passing in role resolver with isOwner #3211

Checklist

• New tests added or existing tests modified to cover all changes
• Code conforms with the style
  guide

[bajtos]

This branch is not covered by any test, coveralls reports "Coverage decreased (-0.04%) to 89.558%" as a result. I think we can ignore that, but please let me know if you disagree!

(The solution is to add a test that explicitly calls Role.isOwner(modelClass, modelId, userId, principalType, callback).)

[ebarault]

sorry to wake after the battle @bajtos
i see here that you fix the content of passed options to solely the accessContext (which i agree is the base configuration) when registering the $owner role resolver.
What if a user wants extra customization on top of that to get extra parameters in the passed options? Should he then override the Role model to specify his own way of registering this role resolver?