Incorrect fix of null-safety rule

[kgevorkyan]

Describe the bug

Consider the following code:

while (someCondition) {
    result = someFunction()
    if (result != null) {
        doSomething()
    } else {
        break
    }
}

Expected behavior

TBD

After the mvn diktat:fix@diktat this block changes to the following, which couldn't be compiled:

Observed behavior

while (someCondition) {
    result = someFunction()
    result ?.let {
        doSomething()
    }
        ?: run {
            break
        }
}

Error: break or continue jumps across a function or a class boundary

[petertrr]

Another note: we should not wrap single statements in run when fixing such issues. The provided example will then be fine: ?: break compiles. If there is any logic before break, though, it'll still not work.