Update dependency com.lmax:disruptor to v4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.lmax:disruptor (source)	3.4.4 -> 4.0.0

---

Release Notes

LMAX-Exchange/disruptor (com.lmax:disruptor)

v4.0.0

Compare Source

• Minimum Java version now 11
• Issue #​323 - WorkerPool and WorkProcessor have been removed, no more Disruptor::handleEventsWithWorkerPool
• Disruptor constructors using Executor have been removed. Use ThreadFactory instead.
• Rolled up event handling extension interfaces on to EventHandler:
  • BatchStartAware
  • LifecycleAware
  • SequenceReportingEventHandler
• FatalExceptionHandler and IgnoreExceptionHandler now use the JDK 9 Platform Logging API, i.e. System.Logger
• Add rewind batch feature to the BatchEventProcessor
• Add a maximum batch size argument to BatchEventProcessor
  • EventHandler::onBatchStart now gets both the batchSize as well as queueDepth (previously it had batchSize which reported queue depth)
• Added documentation to EventPoller
• Util::log2 throws if passed a non-positive argument
• Deprecations
  • Deprecated ThreadHints.onSpinWait()
  • Deprecated Disruptor.handleExceptionsWith() - this had been javadoc deprecated since 2015 but not in the code
  • Removed previously deprecated methods
    • Ringbuffer.resetTo()
    • ConsumerRepository.getLastSequenceInChain()

---

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.

[breedx-splk]

@jackshirazi @SylvainJuge @JonasKunz It looks like the next major version of disruptor here only supports java 11+. Do you want to stay locked on the old version or think about leaving java 8 behind?

[JonasKunz]

We should stay with the previous version and compatible with Java 8, otherwise this extension becomes incompatible with the autoinstrumentation agent.

[trask]

I've submitted #1384