[SPARK-34251][SQL] Fix table stats calculation by TRUNCATE TABLE

[MaxGekk]

What changes were proposed in this pull request?

1. Take into account the SQL config spark.sql.statistics.size.autoUpdate.enabled in the TRUNCATE TABLE command as other commands do.
2. Re-calculate actual table size in fs. Before the changes, TRUNCATE TABLE always sets table size to 0 in stats.

Why are the changes needed?

This fixes the bug that is demonstrated by the example:

1. Create a partitioned table with 2 non-empty partitions:

spark-sql> CREATE TABLE tbl (c0 int, part int) PARTITIONED BY (part);
spark-sql> INSERT INTO tbl PARTITION (part=0) SELECT 0;
spark-sql> INSERT INTO tbl PARTITION (part=1) SELECT 1;
spark-sql> ANALYZE TABLE tbl COMPUTE STATISTICS;
spark-sql> DESCRIBE TABLE EXTENDED tbl;
...
Statistics	4 bytes, 2 rows
...

2. Truncate only one partition:

spark-sql> TRUNCATE TABLE tbl PARTITION (part=1);
spark-sql> SELECT * FROM tbl;
0	0

3. The table is still non-empty but TRUNCATE TABLE reseted stats:

spark-sql> DESCRIBE TABLE EXTENDED tbl;
...
Statistics	0 bytes, 0 rows
...

Does this PR introduce any user-facing change?

It could impact on performance of following queries.

How was this patch tested?

Added new test to StatisticsCollectionSuite:

$ build/sbt -Phive -Phive-thriftserver "test:testOnly *StatisticsCollectionSuite"
$ build/sbt -Phive -Phive-thriftserver "test:testOnly *StatisticsSuite"

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39103/

[SparkQA]

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39103/

[MaxGekk]

@dongjoon-hyun @sunchao @cloud-fan @HyukjinKwon Could you review this fix, please.

[sunchao]

LGTM (non-binding) - thanks @MaxGekk

[cloud-fan]

thanks, merging to master!