Ziti Controller in HA mode doesn't update binding address in a bolt database after config changed

[nenkoru]

Continuation of #2585.

I have encountered an issue when changing the address in a config file when using HA/Raft mode doesn't update the values in bolt database. Took quite a while to debug.
Could be replicated at current HEAD at 1932a6d

Steps to replicate:

1. Start a controller in a raft mode with binding's address with a port(eg 443)
2. Stop the controller
3. Change the port of the binding's address to another(eg 4433)
4. Start the controller
5. Query /edge/client/v1/controllers/ and see that it outputs the old port
6. (Optional) just use a search within ctrl.db file for the old port and see that its unchanged
7. (Optional) Use ziti ops db explore ctrl-ha.db and see that ziti.controllers.ctrl1.apiAddresses.edge-client.0 still lists old address values[1] vs new ones [2].

[1]

ziti...apiAddresses.edge-client.0> list

Key                   Type    Value
apiAddresses.url      string  https://127.0.0.1:443/edge/client/v1
apiAddresses.version  string  https://127.0.0.1:443/edge/client/v1

skipped: 0, limit: 100

[2]

web:
  - name: all-apis-localhost
    bindPoints:
      - interface: 0.0.0.0:1281
        address: 127.0.0.1:4433
    options:
      minTLSVersion: TLS1.2
      maxTLSVersion: TLS1.3
    apis:
      - binding: health-checks
      - binding: fabric
      - binding: edge-management
      - binding: edge-client
      - binding: controller-health
      - binding: edge-oidc

[plorenz]

I probably broke this when I was trying to reduce unnecessary updates. I'll take a look. Thank you for reporting.

[nenkoru]

I probably broke this when I was trying to reduce unnecessary updates. I'll take a look. Thank you for reporting.

I could actually try to fix the issue if you could share the commits that potentially introduced it!