chore(smoketest): update quarkus pods env vars for agent HTTPS connection

[mwangggg]

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

---

Related to: cryostatio/cryostat-agent#141
Depends on cryostatio/cryostat-agent#257

[github-actions]

Hi @mwangggg! Add at least one of the required labels to this PR

Required labels are : chore,ci,cleanup,docs,feat,fix,perf,refactor,style,test

[github-actions]

Hi @mwangggg! Add at least one of the required labels to this PR

Required labels are : chore,ci,cleanup,docs,feat,fix,perf,refactor,style,test

[github-actions]

Hi @mwangggg! Add at least one of the required labels to this PR

Required labels are : chore,ci,cleanup,docs,feat,fix,perf,refactor,style,test

[github-actions]

This PR/issue depends on:

• feat(HTTPS): implement HTTPS keystore cryostat-agent#257
  By Dependent Issues (🤖). Happy coding!

[andrewazores]

If the quarkus-test application is going to have certs added to it like this, then the cert should either be embedded into the application build itself (not coming from the agent, but rather the combination of raw application plus agent into a container image), or the cert should be overlaid on top of the application container image by using a --mount like in run.sh. If you go the --mount way then the certificate used can actually be generated within the smoketest script, or the script can check if a cert exists in some local directory.