Prompt field order number impossible to maintain

### Is your feature request related to a problem?

The requirement of adding a order number to each prompt field makes it impossible to reuse prompt fields across different stages. I was trying to use the same prompt field in multiple places but the order gets messed up forcing to duplicate the field. This really is not maintainable in the long run as the number of stages grow.

### Describe the solution you'd like

Can there be an enhancement to separate the ordering from the prompt fields ? Maybe have each stage maintain the order of its prompt fields within it so the UI is decoupled from the data of the fields.

### Describe alternatives that you've considered

I've tried to duplicate prompt fields to use across different stages but as a create more stages it becomes too difficult to maintain. I was trying to create user details with the username , but that is also used in enrollment, login, so I duplicated it. But now was adding another user details stage for a different case and order of fields is getting very messy and very difficult to change since i have to retest all other stages and readjust the order of other fields which triggers a chain reaction of order changes just for trying to add one prompt field.

### Additional context

_No response_

No files or tests are named in the issue. Start by tracing how prompt fields and their order are stored for each stage and how the UI reads them; define the scope before changing the model. Done means one prompt field can be reused across stages while each stage preserves its own order without requiring duplicated fields.

Written by the indexing model from the issue text.