Remove conflict with doctrine/orm >= 2.16.0

[franmomu]

Reverts #2661 (there was no release)

should we add a conflict with 2.16.0 and 2.16.1?

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +0.01% 🎉

Comparison is base (5502bae) 79.55% compared to head (cbcb4a1) 79.56%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2687      +/-   ##
==========================================
+ Coverage   79.55%   79.56%   +0.01%     
==========================================
  Files         161      161              
  Lines        8409     8409              
==========================================
+ Hits         6690     6691       +1     
+ Misses       1719     1718       -1     

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[phansys]

should we add a conflict with 2.16.0 and 2.16.1?

Sorry, I'm not following the history of the issue.
Is there a change in a 3rd party dependency that motivates this change or is it a improvement for the approach provided in #2661?

[franmomu]

should we add a conflict with 2.16.0 and 2.16.1?

Sorry, I'm not following the history of the issue. Is there a change in a 3rd party dependency that motivates this change

yeah, for reference: #2659

So in doctrine/orm 2.16.0 doctrine/orm#10547 cause multiple failures in our tests (apart from relying on autoincremental id) and after doctrine/orm#10915 (released in 2.16.2) these tests are passing green again, so there is no need for the conflict anymore.

[phansys]

Thanks for the clear explanation.
I agree we should prevent the conflicting versions then. I guess we can update the constraint in the require section to disallow the offending versions.

[phansys]

Thank you @franmomu!