Support "Environments" to allow for autocompleting params in workflows

Dupe Check

• I have searched Warp feature requests and there are no duplicates

Describe the solution you'd like?

Add the concept of Environments, sets of variables for substitution, like Postman does. This would allow to use common workflows on many different projects, without having to enter param values each time. I'm not suggesting to use the shell environment variables, even it could be useful note is quite the opposite, I'd like to be able to set the same variable name with different values based on a sort of workspace name.

Is your feature request related to a problem? Please describe.

I work with many projects which I have common workflows defined for. Sometimes the workflow will do something with the name of the project, other times with the base URL associated, project ID, etc.
Right now I have the params for each of the projects saved in notebooks, but I can easily see how them could be picked up by the workflow (they all have matching names with the params)

Additional context

I'm using Warp myself and having this would trigger the adoption on my company.

How important is this feature to you?

4

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

The issue names no files, tests, or entry points. Start by locating Warp's workflow and parameter-substitution implementation, then clarify how environment sets and workspace selection should be represented; done should include reusable workflows that autocomplete and substitute project-specific values.