Optimise path parsing

As Jukka mentioned on OAK-978, is often on the critical path and the changes done there had a bad impact on performance:

Apache Jackrabbit Oak
# ReadPropertyTest               min     10%     50%     90%     max       N
Jackrabbit                         4       5       5       6      14   11287
Oak-Tar                           14      15      16      16      27    3855

Until we are able to come up with a better solution that separates parsing from name mapping, I suggest to use the following heuristic to shortcut path parsing: shortcut iff the JCR path does not start with a dot, does not contain any of {}[]/ and if it contains a colon the session does not have local re-mappings.