[BUG] Second-level StopRecordOperationException is not caught in CLI

[mabolek]

Describe the bug

When calling interest:create --update on a remote ID that exists or interest:update --create on a remote ID that doesn't exist and a StopRecordOperationException is thrown (e.g. by StopIfRepeatingPreviousRecordOperation) the exception is not caught and the script fails.

To Reproduce
Run a repeated interest:create --update CLI call that will trigger StopRecordOperationException in StopIfRepeatingPreviousRecordOperation.

Expected behavior

StopRecordOperationException should always be caught.