[core] Reject per level avro format with high precision timestamps

[ArnavBalyan]

Purpose

• Avro cannot store timestamps with precision over six.
• Per level avro setting not checked and was allowing invalid table creation with incompatible precision.
• Validate the precision upfront and fail with clear message, if configuration cannot be satisfied.
• Closes user reported bug [Bug] TIMESTAMP(9) write to PostponeBucketTable fails with 'file.format.per.level' = '0:avro' #7883

Tests

• UT

[JingsongLi]

+1