FIX: addressing the state input deadlock bug

[ZLLentz]

Description

When the user resets an error, bring the states input handler FB back to a known state.

Motivation and Context

Will close #197

In short: previously, we could get into a deadlocked state where the input FB would always keep bExecute high, which means the move FB would never be able to get a rising edge.

How Has This Been Tested?

• Unit test that fails before and passes afterwards
• Interactive testing with the example motion plc code

Where Has This Been Documented?

Detailed documentation in the unit test

Pre-merge checklist

• [x] Code works interactively
• [x] Test suite passes locally
• [x] Code contains descriptive comments
• [x] Libraries are set to Always Newest version (Library, *)
• [x] Committed with pre-commit or ran pre-commit run --all-files

[tylerjohnson3208]

Whoops... logged in my personal account.