chore: remove soak-interrupts.yaml

[cmwylie19]

Description

The intention behind the soak-interrupts test was to test the informer pattern by disconnecting the watch and using the LAST_SEEN_TIME and relist to trigger trigger fetch calls against watch resources t update the ephemeral informer cache and dispatch missed events.

There is currently no way to "turn off" the watch connection without also turning off the "list" which both communicate to the kube-apiserver. If there were a way it would need to be a new feature in KFC.

The way this test is written now it scales down the Pepr pod and brings it back up and expects the events to be processed. This case is tested in nearly every excellent example that has a watch and in the UDS test. There is nothing unique about this test.

Related Issue

Fixes #1708

Relates to #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Unit, Journey, E2E Tests, docs, adr added or updated as needed
• Contributor Guide Steps followed

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.44%. Comparing base (26989a0) to head (38d921e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1714   +/-   ##
=======================================
  Coverage   79.44%   79.44%           
=======================================
  Files          48       48           
  Lines        2082     2082           
  Branches      450      459    +9     
=======================================
  Hits         1654     1654           
  Misses        398      398           
  Partials       30       30           

[samayer12]

Discussed sync as a team, this is good to remove.