Explore switching back our Run OPA tests action from back from < 0.50 to latest

[buidav]

💡 Summary

Back during the 0.30 release we had to switch the Run OPA tests workflow from latest to < .50 #193.
Over the course of the Emerald release, we've might've solved this issue with our Rego code updates.
This issue is to see if we can switch back from < .50 to latest.

Motivation and context

To revert a change we made because we were out of compliance with OPA standards.

Implementation notes

Change that variable and see if our current rego code still fails.

Acceptance criteria

• < 0.50 => latest in run_opa_tests.yaml

[mitchelbaker-cisa]

Changing the OPA version from <0.50 to latest in run_opa_tests.yaml throws the same errors which are fixed in #631. Once this PR is merged then we should be fine switching the test action back to latest. (I pulled my changes from this PR to double check and the test action passes successfully)

[schrolla]

PR #631 has been merged to flipper branch, so this should be cleared to move ahead. Would also recommend updating the default expected version in the OPA.ps1 script to reference the latest version of the OPA engine by default so that version is downloaded on setup instead of the old version.

May need to wait/deconflict for PRs #197 to be merged to cleanly update the script version.