feat(autoconfig): wizard supports callback-port, harvester-template, harvester-max-files labels

[andrewazores]

Welcome to Cryostat! 👋

Before contributing, make sure you have:

• Read the contributing guidelines
• Linked a relevant issue which this PR resolves
• Linked any other relevant issues, PR's, or documentation, if any
• Resolved all conflicts, if any
• Rebased your branch PR on top of the latest upstream main branch
• Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• Signed all commits using a GPG signature

To recreate commits with GPG signature git fetch upstream && git rebase --force --gpg-sign upstream/main

---

Depends on #833
Based on #833
Depends on cryostatio/cryostat-operator#1277

Description of the change:

1. Refactors the deployment action to rely only on the Cryostat Operator pod labels (ie cryostat.io/namespace, cryostat.io/name, cryostat.io/harvester-template) instead of using both pod labels and environment variables
2. Adds support for harvester periodic push period, harvester periodic push max files, and Agent HTTP callback port

[jtolentino1]

LGTM. Tested on an OpenShift cluster with Cryostat Operator installed. Applied the wizard-style labels to a Deployment and verified the Operator injected the Agent with callback port + harvester period/max-files settings.

Just one minor comment below

[jtolentino1]

Should this parse Kubernetes quantity suffixes instead of using parseInt? The wizard writes this label with formatByteSizeForLabel(), so values like 20Mi can be saved. When the modal opens again, parseInt('20Mi', 10) becomes 20, so the wizard treats it as 20 bytes instead of 20 MiB.