deps: update dependency io.perfmark:perfmark-api to v0.26.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.perfmark:perfmark-api	0.25.0 -> 0.26.0

---

Release Notes

perfmark/perfmark

v0.26.0: Release 0.26.0

Compare Source

API Changes

• PerfMark.setEnabled() now returns if setting the value succeeded. (#​181).

Implementation Improvements

• Added work arounds for Java 19's Virtual threads, which may not be able to
  use Thread Local storage. If this is the case, PerfMark attempts to
  emulate thread local trace buffers using a concurrent map.
• Trace storage now more eagerly removes storage when it find the thread
  is gone, and is more GC friendly. PerfMark still attempts to preserve
  trace data after a thread finishes, but without strongly referring to it.

Unstable API Changes

The following changes are to unstable APIs of PerfMark. This section
describes APIs for advanced users to try out new functionality before
it becomes API stable.

• Added Methods to Storage for clearing thread local and global storage (#​177)
  • Storage.clearLocalStorage() enables individual threads to clear their storage
  • Storage.clearGlobalIndex() marks storage as SoftlyReachable where possible
    It can be used to indiciate that future calls to Storage.read() should not
    include data after the point that the global index was cleared. Both
    clearLocalStorage and clearGlobalIndex can be used to remove old trace
    data.
  • LocalMarkHolder was added to enter and exit critical sections of of
    MarkHolder mutation. The only implementation currently pulls the MarkHolder
    out of thread local storage for editing. However, this designed to work with
    other context-specific storage mechanisms, such as Kotlin's Coroutines.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.