BUGFIX: Add dimensions to Workspace module

[pKallert]

resolves: #3470

This adds Dimension handling to the current workspaces module.

Currently the Module only displays changes in different languages as one change. This is because the node path is the same in different languages after they are copied.

Checklist

• Code follows the PSR-2 coding style
• Tests have been created, run and adjusted as needed
• The PR is created against the lowest maintained branch
• Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
• Reviewer - The first section explains the change briefly for change-logs
• Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

[markusguenther]

It works fine, and we have just nitpicks in the code.

[markusguenther]

Before:

After:

[markusguenther]

Would be nice if someone can have a second look @kdambekalns @mhsdesign @kitsunet 🙏

[markusguenther]

No one else available for a review @kitsunet @kdambekalns or @Sebobo
It would be nice to have a second review, thanks in advance. :)

[kitsunet]

I have actually done something like this before in a customer project, I have to compare and remember the edge cases I encountered, so I need a moment, I am pretty sure there were some problems with this (eg. if you create a document in a dimension that also has another dimension as fallback, and then underneath two documents for both dimensions, you shouldn't publish the fallbck sub document as it would miss a parent in that case, stuff like that. this case becomes even worse for content and fallbacks).

[markusguenther]

Certainly, @kitsunet ! It's great to hear that you have experience with a similar scenario in a customer project. Your insights into potential issues are valuable. To proceed, could you please provide more details about the specific problems you encountered during that project? Understanding the edge cases and challenges you faced will help us address those issues effectively and come up with solutions to ensure a smooth implementation. Please don't hesitate to share any specific scenarios, complications, or concerns you remember encountering. This will enable us to discuss and brainstorm potential solutions to tackle those issues and ensure a successful outcome for your current project.

[markusguenther]

Rebased changes so that the PR is mergeable until we find a solution for the discussion :)

[mhsdesign]

How do we want to proceed here? This will definitely be not easy to upmerge so we need to reimplement this for neos 9 as well.

[markusguenther]

In the Neos 9.0 weekly we talked today about the PR and @kitsunet mentioned that he is fine with merging it.