IBX-2634: Added argument to functions to ignore ownership

[mateuszdebinski]

Question	Answer
JIRA issue	IBX-2634
Type	bug/improvement
Target Ibexa version	v3.3
BC breaks	no

In order not to change the interface and not to cause BC, only the functions have been changed so that you can pass the argument to ignore the owner - the mechanism itself already existed in our product

Checklist:

• Provided PR description.
• Tested the solution manually.
• Provided automated test coverage.
• Checked that target branch is set correctly (master for features, the oldest supported for bugs).
• Ran PHP CS Fixer for new PHP code (use $ composer fix-cs).
• Asked for a review (ping @ezsystems/engineering-team).

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[alongosz]

AFAIR any change needs to be reflected on an API interface, because we use ProxyManager which won't see them otherwise. But... @adamwojs could you validate that statement? ;)

Question: what is the use case?

[mateuszdebinski]

@alongosz

If I remember correctly, the API interface change won't go through because of BC.

In migration, we allow setting creatorId or modifierId, if a user does not have the appropriate permissions then we throw an exception. However, I probably went a bit too far, because as I read the ticket now, the client would like that if the user does not exist or does not have permission to create/edit, should be used, default user in migration (admin) or from --user-context option

[alongosz]

It feels to me that this should be fixed in ibexa/migrations.
POV ping @Steveb-p

[mateuszdebinski]

I close this PR as we can do it in the migration bundle itself