Update git submodules

* Update plugins/replication from branch 'master'
  to 0f76d57321863a8b49a27d4c550148214be059dc
  - Merge branch 'stable-3.3'
    
    * stable-3.3:
      Remove dependency on commons-io library
      Fix replication to retry on lock errors
    
    Change-Id: I52fea645ccb55c1380702c071f1c7f7f134dc1b2
    
  - Merge branch 'stable-3.2' into stable-3.3
    
    * stable-3.2:
      Fix replication to retry on lock errors
    
    Change-Id: Iab364714135d693e011e8abbf7782ae620d009c4
    
  - Merge branch 'stable-3.1' into stable-3.2
    
    * stable-3.1:
      Fix replication to retry on lock errors
    
    Change-Id: Icacd9095feaefd240803405c5b0a16cc0b3a9ed8
    
  - Merge branch 'stable-3.0' into stable-3.1
    
    * stable-3.0:
      Fix replication to retry on lock errors
    
    Change-Id: Ib4b2c1fcac5da6551f72bce68a101b93e9b43b19
    
  - Merge branch 'stable-2.16' into stable-3.0
    
    * stable-2.16:
      Fix replication to retry on lock errors
    
    Change-Id: I6e262d2c22d2dcd49b341b3c752d6d8b6c93b32c
    
  - Remove dependency on commons-io library
    
    This dependency was added in Id12780948a4 to support remoteNameStyle
    "basenameOnly". The only reason for this dependency is to translate
    project name from "foo/bar/myrepo" to myrepo.
    
    It seems to be overkill to add 169 KB to the plugin distribution
    for one single method.
    
    Another disadvantage is that the version of common-io library used
    for this is 2.2 from 2012. If gerrit installation site is using some
    other plugins in addition to replication plugin, then it can easily
    lead to classpath collision, when different versions of commons-io
    libraries are included as transitive dependencies of different plugins.
    
    To rectify, use a replacement method from guava library.
    
    Change-Id: Id254dc38831832a9855bd204e4c2129ec64b88ae
    
  - Fix replication to retry on lock errors
    
    Versions of Git released since 2014 have created a new status
    "failed to update ref" which replaces the two statuses "failed to lock"
    and "failed to write". So, we now see the newer status when the remote
    is unable to lock a ref.
    
    Refer Git commit:
    https://github.com/git/git/commit/6629ea2d4a5faa0a84367f6d4aedba53cb0f26b4
    
    Config 'lockErrorMaxRetries' is not removed as part of this change
    as folks who have it configured currently don't run into unexpected
    behavior with retries when they upgrade to a newer version of the
    plugin. Also, the "failed to lock" check is not removed for folks
    still using a version of Git older than 2014.
    
    Change-Id: I9b3b15bebd55df30cbee50a0e0c2190d04f2f443
    
diff --git a/plugins/replication b/plugins/replication
index 4efef1d..0f76d57 160000
--- a/plugins/replication
+++ b/plugins/replication
@@ -1 +1 @@
-Subproject commit 4efef1d481eefaee287b27488be94f9acb044360
+Subproject commit 0f76d57321863a8b49a27d4c550148214be059dc