fix(matchexpr): include jvmId in js binding

[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 the last commit: git commit --amend --signoff

---

Related to #1377
Related to #1389

Description of the change:

This copies the jvmId field from the ServiceRef object representing a target application into the object binding passed into the JS engine when evaluating a match expression.

Motivation for the change:

Without this, the jvmId property tested in the matchExpression will always be an undefined value, leading to expressions that do not properly test and evaluate against the intended targets. In #1377 Cryostat is still able to use the credentials to authenticate to -agents because the lookup is direct by stored credential ID rather than evaluating the associated expression, but this bug does actually manifest in the web-client since it is visible on the /security view that the agents' stored credentials display as matching against 0 targets.

How to manually test:

1. Run CRYOSTAT_IMAGE=quay.io... sh smoketest.sh...
2. Open web-client and go to /security
3. Observe that the two -agent instances' stored credentials should report 1 match each, and expanding the rows should show that each match is for the expected agent target.

[github-actions]

Test image available:

$ CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat:pr-1393-7b4b9ee1430dba25f353b548c6f81bbb399ddd33 sh smoketest.sh

[tthvo]

Looks good to me! This fixed the issue with serviceUrl not being matched too.