See D4791: Add tenant context to signup codes

• Complete tenant-independence in CLI commands
• Fix regression, cleanup

Be careful when deploying this. Make sure the queue is empty.

This changes nothing if we run the jobs on the main system. But I agree we need a tenant context. See T264 in Phorge.

This make app.passphrase to be used only on production, which is wrong.

I don't think this makes sense, because the same is done by the observer already.

One more note. Currently if topUpWallet() throws exception (for any reason, e.g. Mollie connection issues) the WalletCharge job will try to top up the wallet again. Here it won't happen, so it will be more fragile to temporary issues with the payment provider. Catching the exception and invoking a separate WalletCharge job might make sense.

• Update French localization

10 here is 0.10 CHF, is this the intention?

This most likely conflicts on master.

Merged in rK17dc669efeb3af

• Disable user search route for now

We need to figure out how to use it without ext-sodium

Maybe it makes sense, if huge number of jobs is not an issue. Also we should probably do dispatch($wallet->id) instead of dispatch($wallet) (and do find() instead of refresh()).

A better place to do this is in the libkolab plugin. See https://git.kolab.org/rRPK905644dc6c5e256c42f3a6a422601759ea0a47cd

@mollekopf, This is kinda strange. You have to know tenant ID (to put it in config) before creating any record. Is this working? It might be better to create the default tenant in migration (where we create the tenants table) instead of seeder.

• Add 'tenants' command
• Update doc

All special folders are supposed to be displayed as top-level folders on top of the list. No matter they are in fact top-level folders or not.