tests: Potentially fix flaky ValidtionStrict test

[davidjumani]

Description

Potentially fix the flaky ValidationStrct test by ensuring the kubeCoreFailurePolicy is set to Fail

API changes

Code changes

CI changes

Docs changes

Context

Interesting decisions

Testing steps

Notes for reviewers

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[github-actions]

Visit the preview URL for this PR (updated for commit ee6e317):

https://gloo-edge--pr10598-fix-validation-stric-5racicqj.web.app

_{(expires Thu, 13 Feb 2025 19:14:01 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 77c2b86e287749579b7ff9cadb81e099042ef677}

[sam-heilbron]

I know that flakes can be hard to pin down, and thus prove that they are resolved, so at times we take a bet and then view the results.

Can you share some insight into what the flake is, what we suspect is happening and why this change is expected to have an impact?
Additionally, how will we validate this change? Even if it's just "well check back in on results in 2 weeks" I can live with that