E2E - Artifacts `access` keyword

Follow-up from !145206 (comment 1801352220)

This issue describes the proposal for a new E2E test for pipeline configuration keyword access.

Test steps:

1. Create a new project via API
2. Register a runner to the project via API
3. Create a user, add this user to the project as developer
4. Create a user, don't add this user to the project, this will be the non-member user

Context: when access: none

5. Add .gitlab-ci.yml to the project with keyword access: none, (wait for pipeline to succeed)

Test case: project member cannot access artifact

6. Login as developer user, visit project -> latest pipeline -> job with artifacts
7. Verify developer user cannot access the artifacts

Test case: non-project member cannot access artifact

8. Logout and login as non-member user, visit project -> latest pipeline -> job with artifacts
9. Verify non-member user cannot access the artifacts

Context: when access: developer

10. Add .gitlab-ci.yml to the project with keyword access: developer, (wait for pipeline to succeed)

Test case: project member can access artifact

11. Login as developer user, visit project -> latest pipeline -> job with artifacts
12. Verify developer user can access the artifacts

Test case: non-project member cannot access artifact

13. Logout and login as non-member user, visit project -> latest pipeline -> job with artifacts
14. Verify non-member user cannot access the artifacts

Context: when access: all

15. Add .gitlab-ci.yml to the project with keyword access: all, (wait for pipeline to succeed)

Test case: project member can access artifact

16. Login as developer user, visit project -> latest pipeline -> job with artifacts
17. Verify developer user can access the artifacts

Test case: non-project member can access artifact

18. Logout and login as non-member user, visit project -> latest pipeline -> job with artifacts
19. Verify non-member user can access the artifacts