pass options to the fetch function

[vincentsarago]

closes #397

@emmanuelmathot can you check this :-)

[geospatial-jeff]

Not a strong opinion, but it feels weird to me that fetch_options wraps both requests and boto3 kwargs but only specific keys from fetch_options are forwarded to boto3 while all keys go to requests. I think this could cause some confusion.

A user might pass a boto3 session kwarg and expect it be passed to client but it won't (assuming they aren't passing the client directly). If its really just s3 requester pays that we want to expose I think it makes more sense to have a single boolean argument (s3_requester_pays) and leave fetch_options just for requests (and maybe rename it to requests_http_kwargs or something more explicit)

[vincentsarago]

Ok let me try something else!

[emmanuelmathot]

Sorry for the missed review. Thank you for the effort!