Add sleep 5 after applying e2e-ci-runner RBAC to handle Kubernetes
subject access review caching. Without this delay, the CI runner's
token does not immediately inherit the new permissions, causing
the subsequent 'Apply Polaris dashboard RBAC' step to fail with:
forbidden from roles in rbac.authorization.k8s.io API group
Also add an explicit permission verification step that fails fast
if the CI runner still lacks roles permission after the wait,
rather than letting the error cascade into later steps.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Chris Farhood
599d5e4be7