max-priority for baker is not inclusive and can cause misses
Running -baker with --max-priority 0
does not include blocks with priority 0. The check appears to be "if priority < $max-priority" rather than "prio <= maxPrio".
The following is a log excerpt with our baker set to max=0:
Oct 8 10:36:50 - 004-Pt24m4xi.baking.forge: No slot found at level 641365 (max_priority = 0)
Oct 8 10:37:54 - 004-Pt24m4xi.baking.forge: No slot found at level 641366 (max_priority = 0) <-- we had rights here at this level for prio 0
Oct 8 10:40:05 - 004-Pt24m4xi.baking.forge: No slot found at level 641367 (max_priority = 0)
As seen in the logs, even though it says "max prio is 0" and we had a bake at prio 0, this was skipped and our bake missed.
Please correct this logic in the code so that the comparison is correct and inclusive of the parameter. (ex: max-prio = 1 should match prio 0 and prio 1 rights)