[backport v1.3] [FEATURE] support bundle timeout enhancement

[harvesterhci-io-github-bot]

backport the issue #1646

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
  The HEP PR is at:

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

Prepare:

1. Use new harvester with new support bundle kit image
2. Define settings > support-bundle-node-collection-timeout (unit is minute)
3. Create support bundle
4. Check env fields of support bundle manager deployment.apps
   

Two different cases:
Case A: define large and enough minutes, it should get nodes folder successfully.
Case B: define a small minute, like "1". This one depends how long your environment takes. Just define a very small minute to make timeout happen. Although It won't get nodes folder, but It will get the support bundle file zip.

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR is at:

• feat: add node timeout rancher/support-bundle-kit#109

• feat: add support bundle node collection timeout (backport #5838) #5913

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

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at: v1.3 (v1.3) bump: support-bundle-kit to v0.0.38 #5915

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at: feat: add support-bundle-node-collection-timeout config dashboard#1041

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at: docs: add support bundle node collection timeout setting docs#569

• If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at: