Add block breaks per tick setting

Allow the server to set the maximum number of block breaks per tick. This means large forests will be cut down in "steps" and items will be dropped sequentially instead of all at once.

It may cause congestion issues on servers. people may end up stuck in a queue waiting for their trees to break. There will have to be some sort of dynamic allocation based on the number of blocks the user needs to break, the available breaks for that tick, and the number of users

No files, tests, or entry points are identified. Start by locating the server tick and tree block-breaking logic, then determine how a configurable per-tick limit could allocate breaks among users. Done means large trees break in steps, drops arrive sequentially, and the setting handles multiple users without leaving them indefinitely queued.

Written by the indexing model from the issue text.