test: Migrate logs env tests to e2e tests

[shorim]

Description

Changes proposed in this pull request (what was done and why):

• Migrating LogPipeline env tests:

  • Migrated unsupported Loki output test to an e2e test
  • Migrated secret rotation test to an e2e test
  • Migrated resources test (existence of expected resources and OwnerReferece is set correctly) to an e2e test. I added checks for more resources than the existing ones in the env test.
  • The remaining env tests were simply removed, as they were either checking for static values that are already tested using unit tests or they are implicitly tested in other e2e tests

• Metrics and traces e2e resources tests:

  • Also removed the tests here which were checking for static values that are already tested using unit tests
  • Added further tests to check the existence of metrics service and network policy and that the OwnerReference value is set as expected

• Metrics and traces e2e secret rotation tests:

  • These tests were using a secret with the same name (missing) and in the same namespace (default). This might have caused flakiness of the tests. This is fixed in this PR.

• Telemetry e2e test:

  • Removed the test for unsupported Loki output, as the Telemetry conditions for this case is now checked in the logs unsupported Loki output e2e test.

Changes refer to particular issues, PRs or documents:

• Merge env and e2e tests #1020

Traceability

• The PR is linked to a GitHub issue.
• New features have a milestone set.
• New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
• The corresponding GitHub issue has a respective area and kind label.
• The follow-up issues (if any) are linked in the Related Issues section.
• Adjusted the documentation if the change is user-facing.
• The feature is unit-tested
• The feature is e2e-tested