test: update sqllogictest expectation for negation type coercion

[myandpr]

Which issue does this PR close?

• Fixes CI breakage on main introduced by fix: validate wrapped negation during type coercion #20965.

link: https://github.com/apache/datafusion/actions/runs/23406116823/job/68085237860

Rationale for this change

#20965 moved invalid negation validation into the analyzer/type coercion path.

After that change, the SELECT -'100' sqllogictest case now reports the error through type_coercion, but scalar.slt was still expecting the older error form. This follow-up updates the sqllogictest expectation to match the current behavior.

What changes are included in this PR?

• update the scalar.slt expectation for SELECT -'100'
• keep the expected error aligned with the analyzer/type coercion error shape introduced by fix: validate wrapped negation during type coercion #20965

Are these changes tested?

Yes.

I reproduced the failure locally and verified the updated expectation with:

• cargo test -p datafusion-sqllogictest --test sqllogictests -- scalar

Are there any user-facing changes?

No.

[myandpr]

Hey @alamb This is the follow-up PR for the sqllogictest expectation mismatch as discussed in #20965 (#20965 (comment)). I reproduced the failure locally on the latest main and updated scalar.slt to match the current type_coercion error shape.

Could you please take a look when you have a chance? Thanks.