Loader options

[cisaacstern]

Just a thought I had while reviewing https://github.com/wildlife-dynamics/ecoscope-workflows/pull/1305, one bit of friction that this implementation doesn't solve for is cases where in one workflow we want the mocked value of a task to be x but mock it as y in other workflows.

We actually have this difference with the get-events mock between the events workflow and event-details workflow but are getting away with it today because the latter mocks a meta-task.

....Outside the scope of this PR, what do you think about passing through a loader_options dict or similar from here into the loader?

I'm imagining the options would be defined as tags on @register or similar - which if it sounds familiar was an idea I floated for solving the mock issues with the spatial groupers feature.

Originally posted by @atmorling in #22 (comment)

[cisaacstern]

@atmorling please at context as you see fit!