Remote fetch operations failed with interrupted exception

Currently, `fetch.max.wait.ms` is reused on remote fetches to cancel operations if taking longer than timeout.
Given the default value is 500ms, it may end up being too small for the whole remote operation to complete.

Ideally this would be default by a different configuration. Some alternatives are being discussed here: https://issues.apache.org/jira/browse/KAFKA-15776

Once a better approach for this issue is implemented upstream, update the plugin to support it properly.