Blobfuse-proxy install ignores all apt install errors

[olishenton]

What happened:
blob-csi-driver was installed via helm on an ubuntu node with node.blobfuseProxy.blobfuse2Version=2.5.0 set, but the install failed due to dpkg package lock collision (likely with other Azure driver setup), leaving the node with the image default version of 2.4.1.

What you expected to happen:
blobfuse2 version to be installed with version 2.5.0

How to reproduce it:
Get unlucky with package locks, or hit some other error.

Anything else we need to know?:
Logs:

• echo begin to install fuse3 blobfuse2=2.5.0
• nsenter --mount=/proc/1/ns/mnt apt-get install -y fuse3 blobfuse2=2.5.0
  E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7691 (dpkg)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
• true

Environment:

• CSI Driver version: v1.26.5
• Kubernetes version (use kubectl version): v1.33.1
• OS (e.g. from /etc/os-release): Ubuntu 22.04.5 LTS
• Kernel (e.g. uname -a): 5.15.0-1091-azure
• Install tools: helm
• Others:

[olishenton]

This is a side effect of #1508.

Adding something like -o DPkg::Lock::Timeout=60 to the apt install would mitigate this particular issue, though it may be preferable to remove the || true and find an alternative solution to #1507.

[andyzhangx]

with this #2089, I think we could revert #1508 now