Fix netpol crash when node remains tained uninitialized

[brandond]

Proposed Changes

Fix netpol crash when node remains tained unintialized

It is concievable that users might take more than 60 seconds to deploy their own cloud-provider. Instead of exiting, we should wait forever, but with more logging to indicate what's being waited on.

The current behavior was added in #9076

Types of Changes

bugfix

Verification

See linked issue

Testing

Linked Issues

• k3s crashes if I do not start the cloud-provider #10068

User-Facing Change

Further Comments

[codecov]

Codecov Report

Attention: Patch coverage is 20.00000% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 41.80%. Comparing base (aa36341) to head (eaf72c3).
Report is 9 commits behind head on master.

❗ Current head eaf72c3 differs from pull request most recent head c2feb45

Please upload reports for the commit c2feb45 to get more accurate results.

Files	Patch %	Lines
pkg/agent/netpol/netpol.go	25.00%	3 Missing ⚠️
pkg/etcd/metadata_controller.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #10073      +/-   ##
==========================================
- Coverage   47.71%   41.80%   -5.91%     
==========================================
  Files         173      173              
  Lines       14642    14642              
==========================================
- Hits         6986     6121     -865     
- Misses       6318     7356    +1038     
+ Partials     1338     1165     -173     

Flag	Coverage Δ
e2etests	36.41% <20.00%> (-9.84%)	⬇️
inttests	37.00% <20.00%> (+17.19%)	⬆️
unittests	11.39% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.