NFD helmrelease upgrade times out for a cluster having large number of nodes

**What happened**: NFD helmrelease upgrade times out for a cluster having large number of nodes

**What you expected to happen**: NFD helmrelease upgrade should go through without any timeout issue

**How to reproduce it (as minimally and precisely as possible)**:
1. Create a cluster with large number of nodes (lets take 30)
2. Try helmrelease upgrade with default helmrelease timeout of 5 mins
3. Helmrelease update times out and rollbacks to old version

**Anything else we need to know?**:

**Environment**:
- Kubernetes version (use `kubectl version`):
Client Version: v1.35.2+rke2r1
Kustomize Version: v5.7.1
Server Version: v1.35.2+rke2r1
- Cloud provider or hardware configuration: RKE2 cluster
- OS (e.g: `cat /etc/os-release`): Suse SLES 15SP3
- Kernel (e.g. `uname -a`): Linux 6.4.0-150600.23.53-default
- Install tools: fluxcd source-controller and helmcontroller
- Network plugin and version (if this is a network-related bug): NA
- Others: NA

Reproduce the upgrade on a 30-node RKE2 cluster using the default five-minute HelmRelease timeout. Start by reviewing the FluxCD source-controller and helm-controller behavior and their logs during the rollback. Done means the NFD HelmRelease upgrade completes without timing out or reverting to the old version.

Written by the indexing model from the issue text.