text: Title: minor netpol test improvements
  Body: #### What happened:
  
  In addition to #102286 ,  this is another good getting started issue for someone interested in learning more about networkpolicy testing in the k8s netpol/ package
  
  - `probeConnectivity` is a little bit long.  lets make its args into a struct somehow
  - investigate failure modes for `probeConnectivity` - what if we send it a bad time like `1S` instead of `1s`, and so on.  can we use native go time package to parameterize it so the code doesnt need `timeoutSeconds` and so on.
  - consolidate the code for making the newWindowsFramework `framework.NodeOSDistroIs("windows") {`
  - map parameters in the `Model` struct as constants where appropriate, or see if theres a way we can configure this.  Maybe split model into "LinuxModel" and "WindowsModel" structs.
  - Investigate if theres a way we can "sleep" on test failures by reading an easter-egg env var? its really tedious to recompile and then import the sleep when trying to debug a networkpolicy issue. 
  - Make logging verbosity lower , but smart enough to print periodically important stuf, right now we print a ton of `/agnhost connect s-netpol-4776-z-c.netpol-4776-z.svc.cluster.local:80 --timeout=1 --protocol=tcp`  type statements .
  - add comments that are more comprehensive about windows vs linux tests , and look at other ways to further modularize the tests (i.e. we return 3 probe for linux, 1 probe for windows, why and so on)
  
  #### What you expected to happen:
  
  not a functional issue , but in aggregate this cleanup will be a good way to grow the pool of netpol test maintainers
  
  