Add precision != 0 check when making decimal type

[HaoYang670]

Which issue does this PR close?

Closes #3665.

Rationale for this change

The precision of decimal type should not be zero, which we should check it.

What changes are included in this PR?

1. Add precision != 0 check
2. Update the error message to make it more readable
3. Add tests.

Are there any user-facing changes?

[alamb]

Thanks @HaoYang670

Can you please file a ticket in arrow-rs if you think it should be fixed there as well?

[ursabot]

Benchmark runs are scheduled for baseline = c989b8e and contender = 051f243. 051f243 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

[HaoYang670]

Thank you for review @alamb .

Can you please file a ticket in arrow-rs if you think it should be fixed there as well?

I've filed apache/arrow-rs#2852 to discuss a better way to solve this problem.