[DEP-289] Propagate property options to FE app

[dkosowski87]

Summary

Property information about the possible options was not propagated through POST /workflows/blocks/describe. Therefore the frontend was not providing usable values for select boxes for operations like DetectionsPropertyExtract, ExtractImageProperty, etc. Instead it was falling back to a static description in the roboflow repo. This PR provides a change to operations introspection to resolve this issue.

Frontend PR - https://github.com/roboflow/roboflow/pull/10655

Initial Linear Issue: DEP-289

Changes

• Included property_name_options in the OperationDescription and ExternalOperationDescription, this field is being populated whenever an OperationDefinition contains a property_name that is defined as a reference '$ref': '#/$defs/DetectionsProperty' and that reference resolves into an Enum
• Added missing area_px and area_converted were added to detection property extraction to enable their use in filters and expressions.

Checklist

• test_introspection_operations.py - test for the introduced mechanism
• test_workflow_schema_detections_property.py - double checking if the options value are provided in the shcema for validation
• tested locally with a setup with the app from https://github.com/roboflow/roboflow running against a local server

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ dkosowski87
❌ cursoragent
_{You have signed the CLA already but the status is still pending? Let us recheck it.}