(Refactor)[Nereids] Combine operator and plan

[924060929]

Proposed changes

Issue Number: no issue

Problem Summary:

in #9755, we split plan into plan & operator, but in subsequent development, we found the rule became complex and counter intuition:

1. we must create an operator instance, then wrap a plan by the operator type.
2. relational algebra(operator) not contains children

e.g.

logicalProject().then(project -> {
    List<NamedExpression> boundSlots =
        bind(project.operator.getProjects(), project.children(), project);
    LogicalProject op = new LogicalProject(flatBoundStar(boundSlots));
    // wrap a plan
    return new LogicalUnaryPlan(op, project.child());
})

after combine operator and plan, the code become to:

logicalProject().then(project -> {
    List<NamedExpression> boundSlots =
        bind(project.getProjects(), project.children(), project);
    return new LogicalProject(flatBoundStar(boundSlots), project.child());
})

Originally, we thought it would be convenient for Memo.copyIn() after split plan & operator, because Memo don't known how to re-new the plan(assembling child plan in the children groups) by the plan type. So plan must provide the withChildren() abstract method to assembling children. The less plan type, the lower code cost we have(logical/physical with leaf/unary/binary plan, about 6 plans, no concrete plan e.g. LogicalAggregatePlan).

But the convenient make negative effect that difficult to understand, and people must known the concept then can develop some new rules, and rule become ugly. So we combine the plan & operator, make the rule as simple as possible, the negative effect is we must overwrite some withXxx for all concrete plan, e.g. LogicalAggregate, PhysicalHashJoin.

Checklist(Required)

1. Does it affect the original behavior: No
2. Has unit tests been added: No Need
3. Has document been added or modified: No Need
4. Does it need to update dependencies: No
5. Are there any changes that cannot be rolled back: No

[morrySnow]

we need to set group's logical properties to plan

[924060929]

when the plan copyIn to Memo, the plan will be withLogicalProperties and withChildren(GroupPlan... childrens):

private Plan replaceChildrenToGroupPlan(Plan plan, List<Group> childrenGroups) {
        List<Plan> groupPlanChildren = childrenGroups.stream()
                .map(group -> new GroupPlan(group))
                .collect(ImmutableList.toImmutableList());
        LogicalProperties logicalProperties = plan.getLogicalProperties();
        return plan.withChildren(groupPlanChildren)
            .withLogicalProperties(Optional.of(logicalProperties));
}

so the plan in the memo contains the logicalProperties same as the logicalProperties in the groupExpression, and replace GroupPlan as children

[morrySnow]

why do this?

[924060929]

fix checkstyle. and private enum DateLiteralType's constructor is also private, so can be omitted

[morrySnow]

groupexpression should use original one？

[924060929]

when the plan is changed, the groupExpression must be clear to tell the memo: I create a new plan, don't skip copyIn.

[morningman]

This PR didn't pass the p0 test, because there are some other issue not related to this PR.
So I skip p0 for this PR.

[EmmyMiao87]

LGTM