Issue Description:

Users sometimes write a decision table which generates inefficient DRLs. A bind variable is declared in the previous column and the bind variable is used (only evaluating the variable, not Join) in the later column. Note that these columns are not combined, so result in different patterns.

We can move such a constraint to the right pattern. It would provide correct property reactivity

 (before)
   when
       $fact1 : Fact1( $id1 : id == 1 )
       Fact2( $id2 : id == 2 )
       Fact2( id == 2, convertToIdString($id2) == "id2" ) 
   then

 (after)
   when
        $fact1 : Fact1( $id1 : id == 1 )
        Fact2( $id2 : id == 2, convertToIdString($id2) == "id2" )
        Fact2( id == 2 )
    then

Acceptance Criteria:

• Implement the optimization. Enabled by default.