Updating the test cases for comparison of DMN FEEL range in unary format

[AthiraHari77]

Disabling the below tests as the use case of "!=" semantics need further clarification. [https://github.com//issues/667]
DMN :

<decision name="range_012" id="_range_012">
        <description>Tests FEEL expression: "(!=10) = (!=10)" and expects result: 'true (boolean)'</description>
        <question>Tests FEEL expression: '(!=10) = (!=10)'?</question>
        <allowedAnswers>true (boolean)</allowedAnswers>
        <variable name="range_012"/>
        <literalExpression>
            <text>(!=10) = (!=10)</text>
        </literalExpression>
    </decision>

Test :

<testCase id="range_012">
        <description>unary syntax comparison range NE</description>
        <resultNode name="range_012" type="decision">
            <expected>
                <value xsi:type="xsd:boolean">true</value>
            </expected>
        </resultNode>
</testCase>

Updating the below testcase to return true as both ranges evaluate to same value.
DMN :

<decision name="range_010" id="_range_010">
        <description>Tests FEEL expression: "(=10) = [10..10]" and expects result: 'true (boolean)'</description>
        <question>Tests FEEL expression: '(=10) = [10..10]'?</question>
        <allowedAnswers>true (boolean)</allowedAnswers>
        <variable name="range_010"/>
        <literalExpression>
            <text>(=10) = [10..10]</text>
        </literalExpression>
    </decision>

Test :

<testCase id="range_010">
        <description>equal ranges though syntactically different are equal: EQ </description>
        <resultNode name="range_010" type="decision">
            <expected>
                <value xsi:type="xsd:boolean">true</value>
            </expected>
        </resultNode>
</testCase>

[baldimir]

@dmn-tck/contributors please review.

[baldimir]

Discussion from the meeting:

• Table 42: Examples of range properties values needs to be updated to clarify the behaviour for unary test ranges with all equality operators, including "=", except "!=" as that translates to two ranges.
• "!=" equality operator unary test ranges need to be clarified, because cannot translate into a single range, but they logically represent two ranges, undefined..number && number..undefined.