Fixes: #24185 Cilium-operator crash on empty azure node pools

[forgems]

Empty VirtualMachineScaleSets returns 404 on ListVirtualMachineScaleSetNetworkInterfaces if there are no nodes in it. Continue with next VirtualMachineScaleSet in that case.

Please ensure your pull request adheres to the following guidelines:

• For first time contributors, read Submitting a pull request
• [] All code is covered by unit and/or runtime tests where feasible.
• All commits contain a well written commit description including a title,
  description and a Fixes: #XXX line if the commit addresses a particular
  GitHub issue.
• All commits are signed off. See the section Developer’s Certificate of Origin
• Provide a title or release-note blurb suitable for the release notes.
• Thanks for contributing!

Azure allows for empty user node pools. In that case ListVirtualMachineScaleSetNetworkInterfaces will return 404 when trying to get interfaces associated with given node pool. With this change it will continue with next VirtualMachineScaleSet if this is NotFound error.

Fixes: #24185

Fix Cilium Operator from crashing when encountering empty node pools on Azure

[forgems]

I've tested it manually on azure cluster with k8s 1.24.9

[forgems]

@tommyp1ckles Any ETA for the review of this?

[tommyp1ckles]

@forgems sorry for the delay - I'll take a look.

[maintainer-s-little-helper]

Commit 7819909d33dd15686a6924d496f60bdc1253feac does not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin

[christarazi]

/test