Rollup node: use correct constant to identify active/lost outbox messages

What

The rollup node used the wrong constant to determine if an outbox message had passed its execution deadline and was lost. This MR fixes this behavior to use the correct constant.

Why

In the case where messages were not executed, they would be removed from the executable set too early and appeared as lost in the RPC /local/outbox/pending. A rollup node catching up on unexecuted outbox messages could miss their execution, incorrectly believing they exceeded their deadline. This last issue is less serious as rollup nodes execute outbox messages as soon as possible.

How

Fetching a new constant in the protocol plugin.