E2E: Repeat Commit on Exception in user_inherited_access_spec
What does this MR do and why?
Project authorization updates can sometimes have a slight delay and cause a user to not have the correct level of access immediately, especially in automated scenarios where actions occur in quick succession.
This MR implements a workaround to resolve Failure in api/1_manage/user_inherited_access_s... (#386597 - closed) by retrying the commit request on exception (such as a 403 error).
A longer term solution will be to implement Return Project Authorization Information for Sp... (#393369), where project authorization status is accessible via API. Then, our E2E tests can call this API after a member is added or removed and only continue on with the test when the auth update is complete.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR. -
Test with the new changes passes on staging: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/9384571