Invalidate default domain location when its lifecycle changes

On 9.10, trashing (and untrashing) the default domain makes the Web UI unresponsive.

Indeed, trashing a document results in changing its life cycle to deleted in 9.10 and lower.

If the life cycle changes on a domain, then maybe it is (un)trashed.

Since user workspaces location is based on the default domain's path and (un)trashing a document alters its path, we need to invalidate the user workspaces location.

Note this is equivalent to the fixes done in NXP-25204 for 10.3 except that for NXP-25204, we don't query for trashed domains anymore when it comes to retrieving User workspaces location while we still do for 9.10 to do not introduce a breaking change of behavior in a HF.