docs(example): Add example on how to execute subset of e2e tests

[meeech]

Classifying this as chore
Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed my commits with DCO
• [n/a] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• [n/a] My organization is added to USERS.md.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[github-actions]

Go Published Test Results

1 989 tests   1 988 ✔️  2m 37s ⏱️
   118 suites         0 💤
       1 files           1 ❌

For more details on these failures, see this check.

Results for commit a275f37.

[github-actions]

E2E Tests Published Test Results

    4 files      4 suites   3h 34m 24s ⏱️
  96 tests   80 ✔️   5 💤 11 ❌
402 runs  364 ✔️ 20 💤 18 ❌

For more details on these failures, see this check.

Results for commit a275f37.

[meeech]

The test failure should be a flaky test? No code changes in this.