chore(e2e): remove legacy e2e setup

[abhijith-darshan]

Description

As part of the clean up task, this PR removes the legacy e2e setup

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

Related Tickets & Documents

• Related Issue [FEAT] - Removal of tools superseded by localenv  #875

Added tests?

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

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

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
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes

[IvoGoman]

Please make sure to update the mentions in the documentation as well.
https://github.com/search?q=repo%3Acloudoperators%2Fgreenhouse+e2e+language%3AMarkdown&type=code&l=Markdown

[abhijith-darshan]

Please make sure to update the mentions in the documentation as well. https://github.com/search?q=repo%3Acloudoperators%2Fgreenhouse+e2e+language%3AMarkdown&type=code&l=Markdown

Hey @IvoGoman , working on removing dev-env, it has bit of a larger change as it has deployed documenation. So when I cover that I will tackle it as it has to be completely re-written.