fix: Allow lookup_base args to be in any order

[lgray]

also: use proper client context on workers when using latest dask

Fixes #810.

Turns out bind was just the idea of what I wanted to do rather than the implementation @agoose77.
Probably means I want to re-engineer lookup_base at some point to be less strange.

[lgray]

@martindurant This is what I would like to replace, since it's a workaround for repeated deserialization of possibly very heavy correction functions. If I could instead encode the necessary metadata in a way that doesn't get deserialized every partition the correction/lookup data everything would be significantly cleaner!

Finding a more pleasant solution to this would also help out #798.