Rename geometry workflow API to Catalyst

[maciej-flexcompute]

Summary

• replace the public geometry workflow knobs with workflow="standard" or workflow="catalyst"
• keep the existing REST compatibility field at the serialization boundary while removing nextflow naming from the Python package and tests
• add regression coverage for Project.from_geometry passthrough and the Catalyst-to-REST mapping

Testing

• python3 -m py_compile flow360/component/project.py flow360/component/geometry.py flow360/cloud/flow360_requests.py tests/simulation/test_project.py
• uv run pytest tests/simulation/test_project.py -q

---

Note

Medium Risk
Medium risk because it changes the geometry/project creation API surface and the serialized request payload field name, which could break clients or backend expectations if not deployed in sync. Logic is straightforward and covered by new tests validating the workflow passthrough and useCatalyst mapping.

Overview
Adds a user-facing workflow selector ("standard" or "catalyst") for geometry-based project creation, replacing the prior Nextflow-named flag throughout the Python API.

Updates request serialization to send useCatalyst on NewGeometryRequest when workflow="catalyst", adds validation for allowed workflow values, and extends Project.from_geometry()/internal project creation to pass the workflow through. Adds regression tests ensuring the workflow argument is forwarded and that Catalyst/standard correctly toggle the useCatalyst API payload.

^{Reviewed by Cursor Bugbot for commit 31aa4ac. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9bf84bc. Configure here.}