Fix Core tests that rely on UID1's super user behavior

After aligning with @kristiaanvandeneynde the RenderCacheTest should be removed entirely. See related issue 🐛 UserRolesCacheContext can lead to poisoned cache returns for user 1 Active .

Removing the tests appear to be scope creep though. Believe the test removal should be done in the issue you mentioned.

Then the mentioned issue should be solved first, because we can not fix this issue if not removing the test.

So actually could just leave that one test as is (revert in MR).
Put a todo in it to 🐛 UserRolesCacheContext can lead to poisoned cache returns for user 1 Active that it will be removed
Updated 🐛 UserRolesCacheContext can lead to poisoned cache returns for user 1 Active to make sure they remove the test there.

Then the other 2 can move forward.

@smustgrave I reverted the deletion of the RenderCacheTest. Can you please make respective comments and add todos in the other issues. I am having a hard time understanding your last comment.

Added todo to the test we aren't updating here and updated IS in 🐛 UserRolesCacheContext can lead to poisoned cache returns for user 1 Active

Committed and pushed cbad32ab34 to 11.x and 097371801c to 10.3.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.