TASK: 9.0 remove leftover manual context path string operations

[mhsdesign]

With #2178 we moved into a direction of rather fetching context paths from the server than manually guessing them in the client.

The current 9.0-dev still shows 21 references to code like .split('@')

const contextString = this.props.siteNodeContextPath.split('@')[1];
const subject = `${this.props.options.createNew.path}@${contextString}`;

This will probably lead to hard to discover bugs, so we should rather make sure to NEVER manipulate the contextPath in the client. (possibly even by restricting the split operation? but at least by going through the code while looking at .split('@')

[mhsdesign]

neos-ui/packages/neos-ui-sagas/src/Browser/index.js

Line 5 in 8404fd3

yield call([history, history.replaceState], {}, '', `?node=${encodeURIComponent(action.payload.documentNode)}`);

might also be broken on 9.0

and logic such

neos-ui/packages/neos-ui/src/Containers/ContentCanvas/index.js

Line 178 in 02ef655

const internalLinks = iframe.contentWindow.document.querySelectorAll('a[href*="@user-"]');

as well

[mhsdesign]

This is still an issue - i found it in makeCanBeCopiedSelector - maybe we should fix the 'simple' obvious cases and for every other case add a todo there with a fixme so that someone stubling on that part has an idea that this is bungus