Change default EXPLAIN format in datafusion-cli to tree format

[alamb]

Which issue does this PR close?

• Closes [DISCUSS] Switch to tree explain by default #15343

Rationale for this change

We have nice explain plans, let's default DataFusion cli to use them

What changes are included in this PR?

Note that as discussed on #15343, this ONLY affects datafusion-cli. Any downstream project that wants nicer explain plans by default can adjust the configuration settings

Are these changes tested?

Yes with new tests

Are there any user-facing changes?

EXPLAIN in datafusion-cli will now use the new explain tree format. For example:

DataFusion CLI v46.0.1
> explain select 123;
+---------------+-------------------------------+
| plan_type     | plan                          |
+---------------+-------------------------------+
| physical_plan | ┌───────────────────────────┐ |
|               | │       ProjectionExec      │ |
|               | │    --------------------   │ |
|               | │      Int64(123): 123      │ |
|               | └─────────────┬─────────────┘ |
|               | ┌─────────────┴─────────────┐ |
|               | │     PlaceholderRowExec    │ |
|               | └───────────────────────────┘ |
|               |                               |
+---------------+-------------------------------+
1 row(s) fetched.
Elapsed 0.026 seconds.

You can get the previous indent explain plan by asking for it explicitly:

DataFusion CLI v46.0.1
> explain format indent select 123;
+---------------+------------------------------------------+
| plan_type     | plan                                     |
+---------------+------------------------------------------+
| logical_plan  | Projection: Int64(123)                   |
|               |   EmptyRelation                          |
| physical_plan | ProjectionExec: expr=[123 as Int64(123)] |
|               |   PlaceholderRowExec                     |
|               |                                          |
+---------------+------------------------------------------+
2 row(s) fetched.
Elapsed 0.023 seconds.

[alamb]

I could not get these to work as additional examples in quick_test for reasons I couldn't figure out. So I just made a new test

[blaginin]

probably because of this

https://github.com/apache/datafusion/pull/15427/files#diff-2382ee3b9da4ce9186e2e8abc1bc3e923f2d3d548de8039dc1f2aa7a21b88942R84

[blaginin]

this works

blaginin@4738e46

[alamb]

Thanks, pulled into this branch

[xudong963]

Looking forward to df47 😆

[blaginin]

I think one issue with the current approach is that loading from env will break.

before:

after:

[alamb]

I think one issue with the current approach is that loading from env will break.

this is a good call -- I will fix that

[alamb]

Run extended tests

[alamb]

Run extended tests

[alamb]

I think one issue with the current approach is that loading from env will break.

I pushed a fix and a test for this

[blaginin]

😍

[alamb]

I'll plan to merge this one tomorrow unless anyone else would like time to comment

[alamb]

🚀 📖

THanks again @blaginin and @xudong963