Update plugins.calcite.enabled setting default

[kolchfa-aws]

Closes #11408

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review.

[kolchfa-aws]

@LantaoJin Could you review this PR and answer the following questions:

• Is the feature still experimental?
• Is the plugins.calcite.enabled setting valid and can the users set it to false to disable it? I don't see the setting here.
• Do we need to document the plugins.calcite.all_join_types.allowed setting?

[LantaoJin]

• Is the feature still experimental?

No. Enabling Calcite by default means we expected PPL queries are running integrated with Calcite engine by default since 3.3.0.

• Is the plugins.calcite.enabled setting valid and can the users set it to false to disable it? I don't see the setting here.

As said above, we expected all queries running integrated with Calcite engine. Yes, it can be disabled by setting plugins.calcite.enabled=false. But I think it is unnecessary to callout.

• Do we need to document the plugins.calcite.all_join_types.allowed setting?

Did we document all other configurations in documentation-website? Yes if always update new configurations.

[kolchfa-aws]

Did we document all other configurations in documentation-website? Yes if always update new configurations.

We should document all configurations on the documentation website. The teams developing the feature should submit PRs to update the documentation with every release. Thank you.

[natebower]

LGTM