[BUG] EvalMode.TRY is not handled properly for Spark 3.4.0+, at least for some arithmetic operators

[revans2]

Describe the bug
This is a result of us looking more closely at try_multiply.

try_multiply was added to Spark 3.3.0 https://issues.apache.org/jira/browse/SPARK-38164, but was then changed in Spark 3.4.0 https://issues.apache.org/jira/browse/SPARK-40222 so that numeric arguments would not catch exceptions for their children.

Most multiply operations do not throw exceptions, but some do (like decimal in some corner cases). We currently think that ANSI and TRY are the same and that we should fail on error. This is not true at all and we will do the wrong thing for try_multiply. We need to look at all of the other try_ operations that are not translated using TryEval and rethink things. At a minimum we need to fall back to the CPU unless we have tests and have verified that we do the right thing.