Add CEL tests for snippetsFilter API

[salonichf5]

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: As code owners we want to verify is API validation is working as expected for SnippetsFilter

Solution: Added CEL tests for SnippetsFilter

Testing: Describe any testing that you did.

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

Closes #3671

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

NONE

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.88%. Comparing base (22f6954) to head (5ef8cb4).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3750   +/-   ##
=======================================
  Coverage   86.88%   86.88%           
=======================================
  Files         128      128           
  Lines       16201    16201           
  Branches       62       62           
=======================================
  Hits        14076    14076           
+ Misses       1952     1951    -1     
- Partials      173      174    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[shaun-nx]

@salonichf5 these are really great tests that you have added, however we want to keep these tests focused on results from the x-kubernetes-validations errors

For the SnippetsFilter CR, the error we want to test against is this one:

x-kubernetes-validations:
- message: Only one snippet allowed per context
  rule: self.all(s1, self.exists_one(s2, s1.context == s2.context))

[shaun-nx]

Lets keep the test file name and the function names consistent.

For the file name, it should be tests/cel/SnippetsFilter_test.go and for the function names, we can remove any underscores and keep them camelcase.

[salonichf5]

Lets keep the test file name and the function names consistent.

For the file name, it should be tests/cel/SnippetsFilter_test.go and for the function names, we can remove any underscores and keep them camelcase.

I have named it as per the other files

[bjee19]

nice!

[shaun-nx]

Lets keep the test file name and the function names consistent.
For the file name, it should be tests/cel/SnippetsFilter_test.go and for the function names, we can remove any underscores and keep them camelcase.

I have named it as per the other files

Sorry I should have been more clear.
The file name currently has a capital F in the word Filter. That should lowercase.
So instead of snippetsFilter_test.go it should be snippetsfilter_test.go

I realize in my first comment I said to change it to SnippetsFilter_test.go but I was wrong there. Sorry about that.