[BUG] longhorn-engine integration-test fails after introducing the fix of golangci-lint error

[derekbit]

Describe the bug

fix: golangci-lint error, such as longhorn/sparse-tools@813ac9e, longhorn/go-iscsi-helper#89 and so on, introduce a default case in the select statement to address golangci-lint errors:

	mergedErrc := mergeErrorChannels(ctx, errorChannels...)
	select {
	case err = <-mergedErrc:
		break
	default: <------------
	}

However, including the default case causes the select statement to exit immediately if there's no message in mergedErrc, instead of blocking until a message is received.

To Reproduce

Expected behavior

Support bundle for troubleshooting

Environment

• Longhorn version:
• Impacted volume (PV):
• Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
• Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:
  • Number of control plane nodes in the cluster:
  • Number of worker nodes in the cluster:
• Node config
  • OS type and version:
  • Kernel version:
  • CPU per node:
  • Memory per node:
  • Disk type (e.g. SSD/NVMe/HDD):
  • Network bandwidth between the nodes (Gbps):
• Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
• Number of Longhorn volumes in the cluster:

Additional context

longhorn/longhorn-engine#1098

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

git clone longhorn-engine and run make integration-test

• Does the PR include the explanation for the fix or the feature?

• Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
  The PR is at

longhorn/sparse-tools#103
longhorn/go-iscsi-helper#89

• Which areas/issues this PR might have potential impacts on?
  Area: longhorn-engine
  Issues