Seedvault disables Framework Backup unconditionally even if it is not the active transport

[olifre]

After a recent LineageOS update, I noted my scheduled backups using another transport (not Seedvault) stopped being scheduled. I found that framework scheduling was disabled — it seems this happens whenever I reboot my device, even if I activate scheduling manually again.

This is likely a consequence of: #628

It seems Seedvault is disabling framework scheduling even if it is not the active transport, breaking other backup transports which may rely on framework scheduling.