[Feature Request]: Syntax consistency set/get variables

### What would you like to happen?

The syntax for variables in the 'get variables' step and the set variables step is different.

Suppose you have a variable "${next_url}". If you want to get this variable using the 'get variables' step, you need to write "${next_url}" in the column 'variable' whereas when you want to set this variable using the 'set variables' step, you need to write "next_url" in the column 'variable name'. This syntax is somewhat inconsistent and led to some stupid errors/confusion.

I'd prefer to write ${next_url} in both cases. If more people have this complaint, this might be worthwhile looking at.

### Issue Priority

Priority: 3

### Issue Component

Component: Pipelines

Start by locating the Pipelines implementations for the “get variables” and “set variables” steps and compare how their variable fields are parsed. Done means the same ${next_url} syntax works consistently in both steps, with coverage for the reported behavior.

Written by the indexing model from the issue text.