User requires the ability to chain multiple API calls within a workflow field definition, where the output of one call is used as input to a subsequent call to populate a dropdown.

Use Case: User selects a Jira project from dropdown A, the system fetches the project's permission scheme ID (API call 1), then uses that scheme ID to fetch associated roles (API call 2), and the response is used to populate dropdown B.

Currently, Harness workflow field architecture does not support chaining multiple API calls where the output of one serves as the input to the next. Please add support for this pattern.