Refresh every cached value from what is stored, extension-enabled included.
The cached values are normally refreshed from GSettings' "changed" notification, which is delivered by the dconf service on its own schedule: a process told *by a third party* that a key changed (the daemon being asked to re-execute right after `gpaste-client migrate` rewrote the backend revision) has no ordering guarantee that the notification landed first. Reloading before acting on such a key reads the value that is actually stored.
Nothing is announced but extension-enabled, as ever when it moves: the backend's own "changed" notification announces the rest when it lands.
| this |
a Settings instance |