fix(ingest): handle exceptions in min, max, mean profiling

[mayurinehate]

Before - failure to compute min, max or median resulted in failure to profile entire table.

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[hsheth2]

this code seems reasonable (although not a huge fan of the repetitiveness)

in what cases is it not possible to compute the min/max/mean/etc - can we prevent the call using a check on the column's data type?

With the sqlalchemy query combiner, an issue with any part of the query forces it to fallback to a sequence of uncombined/unoptimized queries, instead of fetching everything with a single query - so it's better to avoid the call than catch the exception

[mayurinehate]

in what cases is it not possible to compute the min/max/mean/etc - can we prevent the call using a check on the column's data type?

For snowflake TIME columns => ProfilerDataType.DATETIME
Max query works correctly but during serialization GE throws exception TypeError: 12:30:00 is of type time which cannot be serialized.