fix: Raise exception for illegal explode usage

[barak1412]

Fixes #19049.

I am not sure if it's the right fix, since I think it is better to be caught earlier.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.80%. Comparing base (f7de80c) to head (a32d256).
Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #19115   +/-   ##
=======================================
  Coverage   79.80%   79.80%           
=======================================
  Files        1531     1531           
  Lines      208563   208565    +2     
  Branches     2913     2913           
=======================================
+ Hits       166437   166448   +11     
+ Misses      41575    41566    -9     
  Partials      551      551           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ritchie46]

explode on non nested types is allowed and is considered a no-op.

[barak1412]

@ritchie46 So the the opened issue is not a bug?
Or it should error only when used in the context of list/array namespace.

[ritchie46]

The arr.explode now goes into the DSL as explode, but should go into a unique Arrray::Explode node in the DSL.

When converting to IR, we can then check if the .arr was actually called on an array type.

[barak1412]

Thanks, I will try to learn this part of the code, and do the fix.
I guess also List::Explode should be added and verified as well.