Stocking hatch & bus disabling

[RecursivePineapple]

This PR allows you to control whether stocking hatches work with machine controller covers.

From my understanding, here's how stocking hatches work:

When the multi does a recipe check, the stocking hatch will update its available stacks. It does a simulated extraction on the AE system, then stores the resulting stack in an array (right group in the UI), along with its amount (in another array). These arrays match 1:1 with the configured stacks (left group). When a multi scans the hatch, it 'consumes' these fake stacks. At the end of the recipe check, the stocking hatch will determine what was consumed by subtracting the starting counts from the ending counts, then extracting & deleting those stacks from the AE system. If this extraction fails, the stocking hatch shuts down the multi with a critical failure.

My change intercepts the initial simulated extraction. If the hatch is disabled, the hatch will function like the AE system had no matching stacks in it - the multi won't see any stacks and will not consume them in its recipe check. This should be a relatively simple change, but I'd like to test this relatively well in the nightlies first.

Code changes:

• Add onEnableWorking to MTEs
• Update justHadNewXYZ in onEnableWorking if recipe checks are expedited
• Prevent changes in disabled hatches from doing an expedited recipe check (see justUpdated())
• Clear shadow stacks when the hatch is disabled
• Add Disabled/Enabled info to status text widget (only shows up when the hatch is online)

Testing done:

• Hatches work fine when not disabled
• Disabling hatches prevents shadow stack population visually (via recipe checks & adding new stacks to the configs)
• Machines don't consume stacks from stocking hatches when the hatches are disabled
• Expedited recipe checks works properly still
• Recipe checks aren't expedited when the option is disabled or unavailable
• Enabling a stocking hatch will immediately cause a recipe check