TYPO3 Core

If a page slug is changed and no SiteConfiguration available in
the page rootline the corresponding DataHandler Hook fails with
a SiteNotFoundException.

This is related to the streamlining of the ext:redirects auto
create chain which invokes site-configurations early in the
factory for creating the change item without properly handling
the exception. This has been a oversight in the streamlining
change.

Use-caches which triggers this are `SysFolders` directly under
the root point (PID 0) with subpages. If the sysfolder is saved
or subpages changes the excetion is thrown.

Auto create chain is based on two options which are bound to a
concrete SiteConfiguration. If no SiteConfiguration is found,
it is the same as both options are disabled or not set. Thus
the factory for the change item should handle the exception
properly and early returning to avoid any handling. Additionally,
the check for both options should also be done early do avoid the
creationg of change item sources (which may be extended by emmiting
events) which would be superflous if no handling is needed.