macdeployqt assumed that relative library paths referred to a Qt
library or framework that was not contained in any specific directory.
This was broken in the case of paths like somedir/libfoo.dylib.

macdeployqt now takes the additional path components into account.

There was also a trailing space after ".dylib " which snuck in after
refactoring to centralize otool output parsing which caused failures
in Qt Creator deployment.

Task-number: QTBUG-53533
Task-number: QTBUG-53563
Change-Id: I4296b7dd805d4866d3bf0db486366c30dece7add
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Reviewed-by: Morten Johan Sørvig <morten.sorvig@qt.io>