Resolving content for a symlinked (linkId) RepoNode

[loeffert]

The RepoNode and at least the content server take care about the value "linkID" which is helpful if you want to symlink a node to another one.

If the user tries to resolve content for a node which has a linkID set he wouldn't be able to recognize that. The content server responds with a status 200 and returns the node not the linked node - which is maybe fine, but the respond code and the item uri should be fixed.

ID => URI => LINK_ID
#1 => /collection => #2
#2 => /collection/men => null

Resolving /collection will end up with status 200 ok, but it should be 302 found and the returned URI should be /collection/men. Otherwise the user would be able to fetch content which should not be addressable directly.