Use aliases for references to the setup flow elevated component

[florelis]

Summary of the pull request

This changes to use aliases for the references to the elevated component, to be able to include both the projection project and the elevated component.

References and relevant issues

Detailed description of the pull request / Additional comments

For the Setup Flow we created a CsWinRT component to communicate with a process that runs elevated. In the main app, this project is used with a reference to the CsWinRT projection, whereas from the elevated process it is used with a direct project reference. If on a project we include both the projection and the project, we get a compilation error due to both projects exposing the same public types.

The previous solution was to include the ElevatedServer project (which included the ElevatedComponent directly) with ReferenceOutputAssembly set to false. This prevented the conflict between types, but it caused a bunch other issues, like getting duplicated payload files because the ElevatedServer and the main app both used the same binaries but we didn't get MSBuild to resolve them.

This changes to include both projects (projection and the project itself), but adding Aliases to them so that we don't get the type conflict, and when using the types we specify which one we want using extern alias.

This also sets the right property for using the Publish Profiles from the ElevatedServer to ensure it is self-contained.

Validation steps performed

PR checklist

• Closes #xxx
• Tests added/passed
• Documentation updated

[florelis]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[florelis]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).