Implement EZP-23266: Add internal LimitationService to decouple getLimitationType()
 Implement EZP-23266: Add internal RoleDomainMapper to decouple build functions
Fix Legacy/User/Handler->addPolicy() not setting roleId property
Move helpers into own namespace and make it clear what they can use
Adjust code for Helpers namespace and code changes
Add Helper\FieldTypeRegistry

Allows to cleanly use this in several places where SPI type is needed.
Note: There are some overlapp with Persistence\FieldTypeRegistry, however getting
rid of the (imho) uneeded Persistence\FieldType, move this FieldTypeRegistry to
FieldType namespace and use in both places is outside of the scope of this commit.
[Integration Test] Fix wrong assumtion in SubtreeLimitationTest->testSubtreeLimitationForbid

This test was passing wrongly as a byproduct of parentId property on UserGroup being loaded
via LocationService. In this case user should have had access to content as subtree of user
group 13 has exactly same path as the subtree used for limitation, while parent location fell
outside of the limitation causing the exception the test where expecting.

Now parentId property is loaded via SPI and don't have this issue, so test has been
changed to limit the rights to members subtree instead, where editor is not placed.
Merge pull request #1063 from ezsystems/services_decoupling

Services decoupling