Fail hard coded strings in compile time in case of arithmetic operations

Change required for below -
Currently if we give hard coded strings in Value function, it is succeeded at compile time and at run time always give null, in my opinion it should fail at compile time as we know Value function always return decimal and string would never be able to parse to decimal [ex. Value("ab")]
Similarly if we give expression (1+2+"ab"), it passes at compile time right now but gives null at run time bcz IR returns Decimal("ab") which again uses same Value function.

Expressions like this should also fail at IR instead of passing at compile time and giving null at run time.

Below behavior is already there so no change required for below
Only fields with String type should be allowed in arithmetic operation as those fields value can be number at run time which can be parsed to decimal (ex. 1+2+field here field is of type string and field value is "5" so at run time expression will give 1+2+5=8)

Start by tracing the Value function and the IR handling for arithmetic expressions containing hard-coded strings. Check how compile-time validation treats Value("ab") and expressions such as (1+2+"ab"), while preserving the existing behavior for string-typed fields; done means invalid literals fail at compile time and valid field expressions remain allowed.