[BUG] `test_deformed_geometry` sometimes fails with codegen error

[shi-eric]

Bug Description

======================================================================
test_deformed_geometry_cpu (warp.tests.test_fem.TestFem.test_deformed_geometry_cpu)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/warp/warp/warp/codegen.py", line 1027, in build
    adj.eval(adj.tree.body[0])
  File "/home/runner/work/warp/warp/warp/codegen.py", line 2814, in eval
    return emit_node(adj, node)
           ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/warp/warp/warp/codegen.py", line 1684, in emit_FunctionDef
    adj.eval(f)
  File "/home/runner/work/warp/warp/warp/codegen.py", line 2814, in eval
    return emit_node(adj, node)
           ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/warp/warp/warp/codegen.py", line 2576, in emit_Assign
    rhs = adj.eval(node.value)
          ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/warp/warp/warp/codegen.py", line 2814, in eval
    return emit_node(adj, node)
           ^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/warp/warp/warp/codegen.py", line 2308, in emit_Call
    out = adj.add_call(func, args, kwargs, type_args, min_outputs=min_outputs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/warp/warp/warp/codegen.py", line 1329, in add_call
    func = adj.resolve_func(func, arg_types, kwarg_types, min_outputs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/warp/warp/warp/codegen.py", line 1319, in resolve_func
    raise WarpCodegenError(
warp.codegen.WarpCodegenError: Couldn't find function overload for 'Trimesh__boundary_side_index' that matched inputs with types: [warp.fem.geometry.tetmesh.Tetmesh.SideIndexArg, int32]

System Information

Example GitHub aarch64 (CPU only) job: https://github.com/NVIDIA/warp/actions/runs/14771402595/job/41472104973

Can also happen on x86-64 + L40

[shi-eric]

34c6e4cfc89be5e881b2312dfa72296dc4f558aa

[shi-eric]

@gdaviet Your fix seems to have worked, I haven't seen this error since then.