Supporting multiple datamodels with same type names

[RonnyB71]

Description

If you generated multiple data models within an app and you happen to name some of the types the same you will get a conflict on the generated C# models. Avoiding types with the same name doesn't seem feasible and we should support this case in order to support the multiple data models scenario. The types are not necessarily the "same" either - a Person type in one model can be different than a Person type in the other model.

Additional Information

This can potentially be solved by using namespacing in the generated models where the model name is used as a namespace in addition to the default Altinn.App.Models like Altinn.App.Models.Hovedskjema.

Tasks

Preview Give feedback

1. Ensure model name is used in namespace for model as suggested above #11732
   area/data-modeling backend breaking-change +3
2. Implement check on unique data model name (frontend) #11733
   0 of 1
   ux +1

Acceptance Criterias

• Multiple models having a type with the same name without actually beeing the same
• If possible, the generation of datamodels from Studio should try to compile to see if the generated models causes a build error
• Data model names must be unique, and user must be given validation error if they try to create data model with the same name as an existing one.