feat(API): update web-client to use v4 API endpoint

[aali309]

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

---

Part of: 550
depends on: 584

Description of the change:

This change adds allows a match expression example to be copied to the clipboard...

Motivation for the change:

This change is helpful because users may want to copy the example for easier use...

How to manually test:

1. Run CRYOSTAT_IMAGE=quay.io... sh smoketest.sh...
2. ...

[Josh-Matsuoka]

Saw a test failure on first run, building again it passed, is this one known to be flaky?

[test] Summary of all failing tests
[test]  FAIL  src/test/Rules/CreateRule.test.tsx (16.171 s)
  ● <CreateRule /> › should submit form when form input is valid and create button is clicked
[test] 
    thrown: "Exceeded timeout of 5000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      209 |   });
[test]       210 |
    > 211 |   it('should submit form when form input is valid and create button is clicked', async () => {
          |   ^
      212 |     const { user } = render({
      213 |       routerConfigs: {
      214 |         routes: [

      at src/test/Rules/CreateRule.test.tsx:211:3
      at Object.<anonymous> (src/test/Rules/CreateRule.test.tsx:82:1)

[andrewazores]

There are a few tests that seem to be occasionally flaky. I can't recall if I have seen that particular one before, but it looks vaguely familiar. I don't know if somehow it has to do with test run ordering, or if maybe because the tests run against a headless browser if there is some delay on the browser DOM rendering side, or else what the root cause could be.