[BUGFIX] Correctly resolve best matching FAL storage

For legacy reasons storage resolving in file abstraction layer still
supports using identifiers like `/fileadmin/img.png` instead of
`1:/img.png` (given, that `1:` corresponds to `fileadmin/` storage).

To resolve the "best matching storage", existing storage paths are
analyzed - however this did not work in the following cases:

+ identifier like `/fileadmin/img.png` on storage using relative
  base-path like `fileadmin/`
+ identifier using absolute path on storage with relative base-path
+ identifier using relative path on storage with absolute base-path

Resolves: #94519
Releases: master, 10.4, 9.5
Change-Id: Id8663b3e7fc40d777288bd498d2250e528f4f4af
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69793


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Benni Mack <benni@typo3.org>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>