Vector pods going into a panic state in RHOCP 4

Issue

• Vector pods show the below log:

  WARN sink{component_kind="sink" component_id=splunk_platform_receiver component_type=splunk_hec component_name=splunk_platform_receiver}: vector::sinks::util::retries: Retrying after error. error=Failed to make HTTP(S) request: connection error: Connection reset by peer (os error 104)
  thread 'vector-worker' panicked at 'all branches are disabled and there is no else branch', src/kubernetes/reflector.rs:26:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  

• Vector pods are not able to collect the logs.
• Panicked error is shown in Vector logs.