Turbovault4dbt swaps multi_key and payload columns

[universe-designer]

stage.py generates the following model

Current state

HD_PERS_LMS_STRUCTURE_STRM:
is_hashdiff: true
columns:
- <Target_column_physical_name 1>
- <Target_column_physical_name 2>
- <Target_column_physical_name ...>

multiactive_config:
multi_active_key:

  - <Multi_Active_Attributes 1>
  - <Multi_Active_Attributes 2>
  - <Multi_Active_Attributes ...>

This is wrong. Multi_Active_Attributes are descriptive attributes, while Target_column_physical_name are used as the multi_active_key

Target state

HD_PERS_LMS_STRUCTURE_STRM:
is_hashdiff: true
columns:
- <Multi_Active_Attributes 1>
- <Multi_Active_Attributes 2>
- <Multi_Active_Attributes ...>

multiactive_config:
multi_active_key:
- <Target_column_physical_name 1>
- <Target_column_physical_name 2>
- <Target_column_physical_name ...>

The change affects datavault4dbt sources as well.

The example in the documentation is confusing. Why does the example show Target_column_physical_name as descriptive attributes if these must be used as the multi_active_key?

It would be great if the datavault4dbt documentation would continue the example from the turbovault4dbt documentation.