feat: v6.3.7

[danielpilla]

• Optimized the load time of the app by batching app metadata in chunks of 100 requests over a single REST connection.
• Added the ability to batch reload app metadata. This was implemented due to reloads timing out with tenants that contained more than 10k apps. If the tenant contains more than 10k apps, this option will be mandatory.

The batch reload process is as follows:

1. On the "* Optional Configuration *" tab, set the vu_app_metadata_initial_days_back variable to 1.
2. Reload the application.
3. Repeat steps 1 and 2 while raising the number, e.g., 1 → 7, 7 → 30, 30 → 60, 60 → 90, 90 → 180.
4. Set the vu_app_metadata_initial_days_back variable to -1 (this indicates all time).
5. Reload the application to complete the batch process.

[github-actions]

PR checklist

Checklist:

• Is the name of this app/solution still App Analyzer?
• Have you updated the version tag in each .qvf file, and followed semantic versioning (e.g. v1.1.1)?
• Is this PR named appropriately? For example:
  • Feature release: feat: add sheet usage event
  • Bug fix: fix: replaced deprecated events
  • Documentation update: docs: updated images in install guide
• Have you reviewed the unbuilt diff generated by the workflow in /diff?

If you wish to merge and release:

• Have this PR approved by a code owner, then merge into main
• Go to releases, an action will generate a draft release with all files in /assets, and any external assets references in release.json
• Make any updates, then submit the release

Common issues:

• After merging, draft release doesn't update - this is usually because
  the action failed due to an old draft release with the same name.
  Delete the draft release, and re-run the action.

[github-actions]

PR checklist

Checklist:

• Is the name of this app/solution still App Analyzer?
• Have you updated the version tag in each .qvf file, and followed semantic versioning (e.g. v1.1.1)?
• Is this PR named appropriately? For example:
  • Feature release: feat: add sheet usage event
  • Bug fix: fix: replaced deprecated events
  • Documentation update: docs: updated images in install guide
• Have you reviewed the unbuilt diff generated by the workflow in /diff?

If you wish to merge and release:

• Have this PR approved by a code owner, then merge into main
• Go to releases, an action will generate a draft release with all files in /assets, and any external assets references in release.json
• Make any updates, then submit the release

Common issues:

• After merging, draft release doesn't update - this is usually because
  the action failed due to an old draft release with the same name.
  Delete the draft release, and re-run the action.