Scheduler Frequency Fixes

[apfitzge]

Problem

• Scheduler is doing work in too large of chunks causing issues in block-packing

Summary of Changes

• Make the limit of transactions scanned in prio-graph does not exceed 1k
• Receive only up to 5k packets in any single call
• Hold decision behaves like the Consume decision (no timeout if non-empty)
• receive completed transactions before scheduling

Fixes #

[mergify]

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.