Get rid of "cache" concept

[tlater-famedly]

The "cache" is a holdover from ldap-poller, and used to keep track of what changed since the last run of the tool, so that we know when to send update and deletion requests instead of import requests.

While this works for now, and is fine as long as ldap-sync is the only tool performing syncs and the "cache" is persisted, the databases will go out of sync the moment this is not true.

The name "cache" is therefore a big misnomer, since the name implies it can be safely removed at a performance penalty, when in reality doing so breaks the tool. We also currently don't have a good way to get things back into sync when issues (e.g. failed requests) occur because ldap-poller doesn't have an interface to bust the "cache".

We should move away from this.

Tasks

Beta Give feedback

1. Famedly-Sync: WIP Refactor getting rid of cache & single-source sync #90
   +0
   
2. Support single-source sync in Tests #81
   +0
   
3. Famedly-Sync: Refactor for ID encoding and sorting #91
   +0
   
4. Debug and fix tests for Famedly Sync after ID encoding changes #86
   +0
   
5. Encoding library that preserves alphabetical order #87
   +0
   
6. Migration executable for encoding old IDs #88
   enhancement +1
   
7. Documentation for changes and migration guide #89
   documentation +1

[tlater-famedly]

Waiting for famedly/zitadel-rust-client#15