Refine default postfix templates selector

There is new settings checkCanBeUsedAsValue
Also expression filtering are split into to parts:
- getNonFilteredExpressions is trivially goes until it reaches
first block body of some declarations
- all additional filtering is merged into Condition that is passed into
PostfixTemplateExpressionSelectorBase super-call

Notable changes for users:
- do not suggest try for non-top-level expressions
- do not suggest var/par/etc for loops

idea/testData/codeInsight/postfix/assertNonTopLevel.kt

@@ -0,0 +1,3 @@
+fun foo(x: Boolean) {
+    foo(x.assert<caret>)
+}

idea/testData/codeInsight/postfix/assertNonTopLevel.kt.after

@@ -0,0 +1,3 @@
+fun foo(x: Boolean) {
+    foo(x.assert    <caret>)
+}

idea/testData/codeInsight/postfix/noParOnLoop.kt

@@ -0,0 +1,5 @@
+fun foo() {
+    for (i in 1..100) {
+
+    }.par<caret>
+}

idea/testData/codeInsight/postfix/noParOnLoop.kt.after

@@ -0,0 +1,5 @@
+fun foo() {
+    for (i in 1..100) {
+
+    }.par   <caret>
+}

idea/testData/codeInsight/postfix/tryOnFor.kt

@@ -0,0 +1,4 @@
+fun foo() {
+    for (i in 1..100) {
+    }.try<caret>
+}

idea/testData/codeInsight/postfix/tryOnFor.kt.after

@@ -0,0 +1,7 @@
+fun foo() {
+    try {
+        for (i in 1..100) {
+        }
+    } catch(e: Exception) {
+    }
+}

idea/testData/codeInsight/postfix/tryOnStatement.kt

@@ -0,0 +1,3 @@
+fun foo() {
+    val x = 1.try<caret>
+}

idea/testData/codeInsight/postfix/tryOnStatement.kt.after

@@ -0,0 +1,6 @@
+fun foo() {
+    try {
+        val x = 1
+    } catch(e: Exception) {
+    }
+}