PIP-211 [feat][tiered-storage] Introduce offload throttling, Part 1

[tjiuming]

Fixes #17362

Motivation

Support offload throttling, to prevent offloading use up all the broker resources(CPU, network).

From the perspective of generality, we can't limit how many bytes write to tiered-storage, it will invade the corresponding implementations(filesystem, streaming, etc.). So we can only to limit how many bytes read from ML, this cannot absolutely limit the traffic per second.

Modifications

1. Move TimeWindow.java、WindowWrap.java、TimeWindowTest.java from broker module to managed-ledger module.
2. Add managedLedgerGlobalOffloadingPermitBytesPerSecond configuration, it works on the broker level.
3. Add globalOffloadingPermitBytesPerSecond into ManagedLedgerConfig.

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (yes)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (no)

Documentation

Check the box below or label this PR directly.

Need to update docs?

• doc-required
  (Your PR needs to update docs and you will update later)

• doc-not-needed
  (Please explain why)

• doc
  (Your PR contains doc changes)

• doc-complete
  (Docs have been already added)

Matching PR in forked repository

PR in forked repository: tjiuming#11

[tjiuming]

@hangc0276 @codelipenghui PTAL

[tjiuming]

I'll create another PR to support restApi/cmd to modify offload policies after the PR merged

[tjiuming]

Tests to be completed.

[codelipenghui]

@tjiuming, Could you please create a proposal for this one? We will introduce a new mechanism, we need to consider how to operate and monitor the new feature.

[tjiuming]

@tjiuming, Could you please create a proposal for this one? We will introduce a new mechanism, we need to consider how to operate and monitor the new feature.

@codelipenghui Yes, I'm re-designing the flow-controller, the current implementation will block read thread and will take effect to other ledger's reading. After that, I'll open a proposal

[github-actions]

The pr had no activity for 30 days, mark with Stale label.

[poorbarcode]

Since we will start the RC version of 3.0.0 on 2023-04-11, I will change the label/milestone of PR who have not been merged.

• The PR of type feature is deferred to 3.1.0
• The PR of type fix is deferred to 3.0.1

So drag this PR to 3.1.0

[github-actions]

The pr had no activity for 30 days, mark with Stale label.

[dao-jun]

Replaced by #22385