Support auto-loading appropriate ims context based on program id mapping

Currently only one Adobe IO JWT can be stored inside the aio config (because only the key `jwt-auth`) is used. For working with multiple accounts in parallel it would be beneficial if multiple JWT authentication configs could be stored in parallel and bound to specific Cloud Manager Program ID.
Maybe supporting a key config naming scheme like `jwt-auth.` would be sufficient. If no such key is found, the fallback could be the key `jwt-auth`.

Beginne damit, zu ermitteln, wo die aio-Konfiguration den Schlüssel jwt-auth liest und wo die Cloud Manager program ID verfügbar ist. Überprüfe den vorgeschlagenen jwt-auth.-Lookup mit jwt-auth-Fallback, während mehrere Konten parallel nutzbar bleiben; füge Tests für beide Auswahlpfade hinzu oder aktualisiere sie.

Vom Indexierungsmodell aus dem Issue-Text verfasst.