Case data view should render fields in form template order

The "data" view should render the case's data in the same field order as the form template. It should also use the same `name`s, instead of the underscore-separated ones. This should be a matter of combining all the actions' templates in order and passing them to the `CaseData` view.

Alternatively, we could just have a `template` property on the case object in the workflow definition. That would probably be ideal, but maybe it's optional, and it should fall back to the same order of the form templates.

Either way, this is definitely not for MVP.

Start by locating the CaseData view and the workflow definition that supplies the case's actions and form templates. Trace how the data view currently chooses field names and order, then review both proposed approaches before deciding which behavior the project should adopt. Done means the data view follows the form template order and uses the template field names, with coverage for the chosen fallback behavior.

Written by the indexing model from the issue text.