Combine the two instances of EnumerableConvention, ARRAY and CUSTOM, into one, INSTANCE.

Each EnumerableRel is now able to implement itself in any row format that is specified when implement() is called. This change reduces the planner's search space; we lose the ability to cost ARRAY and CUSTOM versions of the same relational expression differently, but I don't believe this will cause the planner to miss any significant insights.