Update git submodules

* Update charm-designate from branch 'master'
  - Ensure pool manager is restarted when pools change
    
    The designate pool manager needs to be restarted on all designate
    units when the update pools command is run with a new version of
    the pools yaml.
    
    Previously it was assumed that it was sufficient to trigger a new
    hook execution but in the following scenario the update is missed:
    
    1) Non-leader reacts to a change in pools and renders a new
       pools.yaml but does not run the db update as it is not the leader
    2) leader reacts to a change in pools, renders a new pools.yaml,
       updates the db and finally sets pool-yaml-hash with the new
       value to trigger hooks executions on peers.
    3) Non-leader reacts to leader db change, re-renders pools.yaml with
       the same values as step 1 and does not perform the pool manager
       restart even though it is needed.
    
    The above scenario is fixed by adding a handler looking for a
    change in the pool-yaml-hash and restarting the pool manager if it
    changes. The leadership layer is needed to get the flags raised on
    leader db changes.
    
    The leader can also fail to restart pool manager as services are
    restarted as soon as the config is rendered and before the
    update_pools call is made. This scenario is fixed by adding a
    handler to look for a change in the pools.yaml and restart pool
    manager if it changes. This works because update pools is run in
    the same handler as config render which means the new handler runs
    after this render & update handler.
    
    Closes-Bug: 1752895
    Change-Id: I54b316788ea5176ca63ca761ceceb106ce903f3b

charm-designate

@@ -1 +1 @@
-Subproject commit bd11190753ae6423d266f8a57251c4c2a60b38bf
+Subproject commit 66dab6d3e7b3e4256ab8ddf0e98bfa9edd312c2e