If there is custom configuration for a project, the CMS update silently fails

We have removed the assets tree, since we store assets as inline resources in a document type. Because the updater expects the node to be there our update process silently fails. I've attached a patch file, which is more explicit and checks for all cms frontend node if they are available.