Support Extra data models and subforms in validation

[ivarne]

Work on supporting multiple data models and subforms in backend validations with expressions.

Related Issue(s)

• Layout & Expression changes due to supporting multiple data models #600
• replaces New validation interfaces to support incremental validation on multiple data models #701
• replaces Support backend validation for multiple data models #619

Main changes

The main goal for this PR is to add

New single interface for validation IValidator

With changes in one data element affects the validity of another element, the current hierarchy of validators and only IFormDataValidator supporting incremental validation break down. Adaptors for the old interfaces has been provided so no changes to current apps are required, but they might want to update in order to support incremental validation and read instance data with the IInstanceDataAccessor.

New interface IInstanceDataAccessor

When validation has dependencies across data models, we need a cached way to access the content of data elements that does not require us to download the same data element multiple times for the same request. The implementation is not available from DI, but always passed as an argument in order to eliminate risk of it being reused cross requests because of Singleton services or other unintentionally shared global state.

New DataElementId struct to ensure type safety for a wrapped Guid

36 places in the updated code need to reference the Guid of a data element, and adding type safety is an important step to ensure correctness. An implicit cast is provided from DataElement to simplify usage

New ModelBinding struct in expressions engine

To support the new syntax for referring to a non default data element in components and expressions

{
    "dataModelBindings": {"field": "path.to.data", "dataType": "default"}
    "hidden": ["equals", null, ["dataModel", "path.to.other", "prefill"]]
}

When handling references to a specific fields (eg. for removal) we needed to also add DataReference to combine a Field (path) with a specific DataElementId

New PATCH api endpoint that allows frontend to update multiple data models at the same time

Saving and triggering incremental validation is expensive and some apps might want to batch multiple changes to reduce cost. The code in frontend would also be simplified if it could do a single request, instead of multiple.

ValidationIssueWithSource class for external apis

Previously we had a single class ValidationIssue that included a Source property. Service owners sometimes tries to set this in their validators (because it shows up in intellisense), but as we override it based on IValidator.ValidationSource in our ValidationService it would be good if it wasn't there to confuse. This PR creates a new type ValidationIssueWithSource for external apis (where the source is included) and marks it [Obsolete] in the type returned in the validator interfaces.

Respect new app logic settings for data elements DisallowUserCreate and DisallowUserDelete

This means that users can not create or delete this types. Typically used for prefill, when you want only the org token to be able to modify the number of data elements on an instance.

Minor changes

Used IL code to generate real C# classes based on the json data models in shared tests. Previously different code was used to access properties of the test code as in production, which is not really good for tests.

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[HauklandJ]

LGTM, some minor things to consider

[sonarcloud]

Quality Gate passed

Issues
69 New issues
0 Accepted issues

Measures
0 Security Hotspots
76.4% Coverage on New Code
0.4% Duplication on New Code

See analysis details on SonarCloud