feat: adding math sec expression

[athlcode]

Which issue does this PR close?

Part #4150

Rationale for this change

sec already has a native implementation in the datafusion-spark crate, but was not yet wired into Comet, so queries using it fell back to Spark.

What changes are included in this PR?

Wires the Spark Sec expression to the datafusion-spark SparkSec UDF (Pattern B: register the UDF in jni_api.rs + one-line passthrough in QueryPlanSerde.scala). Also updates the supported-expression docs.

How are these changes tested?

Added a SQL file test (math/sec.sql).

[comphead]

Thanks @athlcode just wondering, is this PR created with wire_datafusion_function skill?

[athlcode]

Thanks @athlcode just wondering, is this PR created with wire_datafusion_function skill?

welcome @comphead. Yes, the PR was created referring the wire_datafusion_function skill

[comphead]

welcome @comphead. Yes, the PR was created referring the wire_datafusion_function skill

thanks for trying it, it tested for simple wiring, and we need to make it also work for more complicated usecases, where datatypes can be partially supported or behavior is different, etc

[athlcode]

welcome @comphead. Yes, the PR was created referring the wire_datafusion_function skill

thanks for trying it, it tested for simple wiring, and we need to make it also work for more complicated usecases, where datatypes can be partially supported or behavior is different, etc

Shall I try by expanding the skill file for more complicated usecases?

[comphead]

Shall I try by expanding the skill file for more complicated usecases?

Thats the end goal, to let it cover most of usecases, leaving manual work as less as possible

[comphead]

Thanks @athlcode
CI pending

[athlcode]

Shall I try by expanding the skill file for more complicated usecases?

Thats the end goal, to let it cover most of usecases, leaving manual work as less as possible

yep completely agree with you