Ignore dialyzer warnings caused by riak-erlang-client

These warning are caused by typespec issues in the tag of
riak-erlang-client being used currently. They have been fixed, but
those fixes are not yet represented by the tag that Riak CS is using.

dialyzer.ignore-warnings

@@ -160,11 +160,11 @@ riak_cs_mp_utils.erl:522: The pattern <Bucket, OwnerStr> can never match since p
 ^riak_cs_lfs_utils.erl:119:
 riak_cs_gc.erl:.*: The pattern ..UUID, _... _. can never match the type ..$
 ############# Due to inadequate specs with our riak-erlang-client tag
-riak_cs_gc_d.erl:369: Function fetch_eligible_manifest_keys/2 will never be called
-riak_cs_gc_d.erl:373: Function eligible_manifest_keys/1 will never be called
-riak_cs_gc_d.erl:381: Function gc_index_query/2 will never be called
-^riak_cs_riakc_pool_worker.erl:33:
-riak_cs_storage_d.erl:332: Function fetch_user_list/1 will never be called
+riak_cs_gc_d.erl:383: Function fetch_eligible_manifest_keys/2 will never be called
+riak_cs_gc_d.erl:387: Function eligible_manifest_keys/1 will never be called
+riak_cs_gc_d.erl:395: Function gc_index_query/2 will never be called
+^riak_cs_riakc_pool_worker.erl:48:
+riak_cs_storage_d.erl:346: Function fetch_user_list/1 will never be called
 riak_cs_wm_ping.erl:46: The pattern 'undefined' can never match the type pid()
 ############## All the others..........
 riak_cs_blockall_auth.erl:23: Callback info about the riak_cs_auth behaviour is not available