chore: add mockery generate directive

[MR2011]

Description

This PR adds go:generate directive to generate the mockery via go generate

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help
• Separate ticket for tests # (issue/pr)

Added to documentation?

• 📜 README.md
• 🤝 Documentation pages updated
• 🙅 no documentation needed
• (if applicable) generated OpenAPI docs for CRD changes

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[copyonwrite]

When I only look at the Makefile, mockery appears out of nowhere. Would it make sense to have an explicit 'go install ...' target in the Makefile for mockery? For me this would make it more transparent, where mockery comes from.

[dorneanu]

When I only look at the Makefile, mockery appears out of nowhere. Would it make sense to have an explicit 'go install ...' target in the Makefile for mockery? For me this would make it more transparent, where mockery comes from.

That makes sense! I suggest an extra target in the Makefile where we install all tooling/debugging related dependencies:

install-deps: 
    go install github.com/go-delve/delve/cmd/dlv@latest
    go install golang.org/x/tools/gopls@latest
    go install github.com/onsi/ginkgo/v2/ginkgo@latest
    # same with mockery 
   ...