[Heartbeat] Update gval to latest version to improve Heartbeat JSON parsing

[justinkambic]

What does this PR do?

Updates gval module to the latest version.

Why is it important?

Updates gval to latest version with the hope that parsing will be improved for users.

Checklist

- [ ] My code follows the style guidelines of this project
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] I have made corresponding change to the default configuration files
- [ ] I have added tests that prove my fix is effective or that my feature works

• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• Make sure JSON functions are evaluated properly

How to test this PR locally

You can create a monitor like:

- type: http
  id: sendgrid-smtp-status
  name: Check Sendgrid SMTP
  fields:
    component: "sendgrid-smtp-status"
  schedule: '@every 10s'
  response.include_body: always
  tags: ["sendgrid-smtp"]
  urls:
    - https://status.sendgrid.com/api/v2/components.json
  check.request.method: GET
  check.response:
    status: [200]
    json:
      - description: Check Sendgrid SMTP status
        expression: '$.components[?(@.name == "SMTP" && @.status == "operational")] != []'

It should have a status of up

Use cases

Ensure we have the latest version of the JSON parser we use.

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @justinkambic? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-06-07T20:57:26.322+0000

• Duration: 103 min 55 sec

Test stats 🧪

Test	Results
Failed	0
Passed	27307
Skipped	2007
Total	29314

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b gval_1.2.2 upstream/gval_1.2.2
git merge upstream/main
git push upstream gval_1.2.2

[elasticmachine]

Pinging @elastic/uptime (Team:Uptime)

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[andrewvc]

FYI, this needed make update in the root of beats. I've done that and pushed.

@pierrehilbert was there a reason you added @fearful-symmetry onto this? I only heartbeat uses gval AFAICT

[pierrehilbert]

Hey @andrewvc, my bad I didn't see that this change was only touching the go.mod and wanted to have someone from the team looking at it with the new process process in place.

[andrewvc]

LGTM

[andrewvc]

LGTM

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b gval_1.2.2 upstream/gval_1.2.2
git merge upstream/main
git push upstream gval_1.2.2