Branch returned although one of the next states simplifies to #bottom

On slack, Petar reported a problem where a branch result returned by (both kore-rpc and) kore-rpc-booster contains two next-states, but one of them simplifies to #Bottom with an isolated simplify request.
This is caused by kore-rpc execution not discovering the #Bottom-ness of this state, otherwise execution would continue.

Observed behaviour:

• Execution stops and a Branching result is returned. One of the states in next-states simplifies to #Bottom in a subsequent simplify request.

Expected behaviour:

• Execution should continue with the non-bottom alternative of the branch.

• to protect against this behaviour in kore-rpc-booster, modify the postExecSimplify mechanism to detect this case and continue execution.
• reproduce this result with kore-rpc and investigate why the bottom state is not found