Fix "has same role as author" condition not working properly

[Convly]

Description of what you did:

Conditions based on author's roles were not working properly. This PR aims to fix this behaviour.

fix #8129

About the SERVER_ERROR mentionned in the issue, the backend is sending back a 403 Forbidden error.
@soupette / @HichamELBSI do you have any insight on this?

[petersg83]

LGTM, waiting for some smol tests 👀

[codecov]

Codecov Report

Merging #8202 into master will decrease coverage by 0.00%.
The diff coverage is 27.27%.

@@            Coverage Diff             @@
##           master    #8202      +/-   ##
==========================================
- Coverage   33.03%   33.03%   -0.01%     
==========================================
  Files        1219     1219              
  Lines       13563    13569       +6     
  Branches     1348     1348              
==========================================
+ Hits         4481     4482       +1     
- Misses       8200     8205       +5     
  Partials      882      882              

Flag	Coverage Δ
#front	24.70% <0.00%> (-0.02%)	⬇️
#unit	54.11% <60.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...c/components/Roles/ConditionsSelect/MenuList/Ul.js	66.66% <ø> (ø)
...er/admin/src/components/CustomTable/TableHeader.js	0.00% <0.00%> (ø)
...ntent-manager/admin/src/components/Search/index.js	0.00% <0.00%> (ø)
...ugin-content-manager/controllers/ContentManager.js	21.67% <0.00%> (ø)
...r/admin/src/components/ComponentSelect/MenuList.js	0.00% <ø> (ø)
...builder/admin/src/components/SelectMenuUl/index.js	0.00% <0.00%> (ø)
...in-upload/admin/src/components/InputMedia/index.js	0.00% <0.00%> (ø)
...n/services/permission/permissions-manager/index.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43ff63c...3cce9ad. Read the comment docs.

[soupette]

#8129

Since the errors are not unified in the app it's really difficult for the front-end to process them, this is why it doesn't catch the forbidden error.

[derrickmehaffy]

#8129

Since the errors are not unified in the app it's really difficult for the front-end to process them, this is why it doesn't catch the forbidden error.

This will probably be something to address in the backend and unifying/standardizing our error response (I know the U&P plugin has some issues there)

[alexandrebodin]

@derrickmehaffy here we can use the status code which are standard not the best message be forbidden is better than server error :)