refactor: move human readable display utilities to datafusion-common crate

[2010YOUY01]

Which issue does this PR close?

Preparation for #18456

Rationale for this change

• Track individual expr's execution time in ProjectExec metrics (in EXPLAIN ANALYZE) #18456 requires this refactor. Now we have dependency physical-plan -> physical-expr -> common, and metrics module lives in physical-plan. We want metrics module to directly accessible from physical-expr crate, so they should be moved to common crate, and the first step for such refactor is to move metrics internal dependencies to common.
• I believe this module is actually commonly needed through the workspace, so datafusion-common should be a good refactor destination.

What changes are included in this PR?

• move physical-plan/src/metrics module to datafusion-common
• Re-export those human-readable display utilities inside physical-plan, to prevent changing dependents.

Are these changes tested?

existing tests

Are there any user-facing changes?

No

[martin-g]

Have you considered extracting this functionality to its own crate that depends on datafusion_common ?
Usually this helps reducing the build time of a project.

[martin-g]

Those should have been named *iB, e.g. TiB, GiB, etc. since they are base-2, not base-10. But maybe it is too late now.

[martin-g]

Or maybe it is not too late. This PR breaks the API anyway.

[2010YOUY01]

It is re-exported in the original place to keep the API stable, so unfortunately it's too late 🤦🏼

[2010YOUY01]

Have you considered extracting this functionality to its own crate that depends on datafusion_common ? Usually this helps reducing the build time of a project.

From cargo build --release --timings, building datafusion-common is not a bottleneck right now, so I think it’s fine to keep everything in there for simplicity, we could consider breaking it after it grow larger someday.

[alamb]

Thanks @2010YOUY01 and @martin-g