feat: Added connection references validator

[tompivny]

Connection references validation

This pull request introduces a new build task called ValidateConnectionReferences

Features

1. Exctracts defined connection references from Customizations.xml
2. Checks logical names of the connection references used in flows' JSON definitions
3. Provides error messages for any mismatches

Usage

To call the target in a solution with Power Automate flows:

<Target Name="BuildDataverseSolution" BeforeTargets="Build" Condition="Exists('$(ProjectDir)$(SolutionRootPath)\Other\Solution.xml')">
    <CallTarget Targets="ValidateConnectionReferences"/>
    <!--Other build targets-->
</Target>

Optionally, if the connection references are defined in a different solution, you can use a custom property ConnectionReferencesSolutionPath.

For example:

<PropertyGroup>
    <SolutionRootPath>Declarations</SolutionRootPath>
    <ConnectionReferencesSolutionPath>../ConnectionReferenceSolution/$(SolutionRootPath)</ConnectionReferencesSolutionPath>
</PropertyGroup>

[TomProkop]

Thank you for the contribution!

I've got only one small suggestion.

We locate the solution files and load them as MSBuild Items here:

tools-devkit-build/src/Dataverse/MSBuildTasks/Props/SolutionFileItems.props

Line 25 in a92259d

<Flows Include="$(DataverseSolutionSourceFolderFullPath)\Workflows\*.json"/>

Then we pass the Items to a .NET task like this:
https://github.com/TALXIS/tools-devkit-build/blob/a92259d0705f03689a05f6582d3e134614882744/src/Dataverse/MSBuildTasks/Targets/ValidateSolutionComponentSchema.targets#L8C9-L8C92

It would be nice to do it the same way. We'll need to migrate to a new structure next year once Microsoft releases new source control format for solutions.

If you don't have time for that, I'll look at it later.

[tompivny]

Thank you for the contribution!

I've got only one small suggestion.

We locate the solution files and load them as MSBuild Items here:

tools-devkit-build/src/Dataverse/MSBuildTasks/Props/SolutionFileItems.props

Line 25 in a92259d

<Flows Include="$(DataverseSolutionSourceFolderFullPath)\Workflows\*.json"/>

Then we pass the Items to a .NET task like this: https://github.com/TALXIS/tools-devkit-build/blob/a92259d0705f03689a05f6582d3e134614882744/src/Dataverse/MSBuildTasks/Targets/ValidateSolutionComponentSchema.targets#L8C9-L8C92

It would be nice to do it the same way. We'll need to migrate to a new structure next year once Microsoft releases new source control format for solutions.

If you don't have time for that, I'll look at it later.

Got it. I tried to implement your suggestion