[#4081] Stop building twice in the dotnet functional test pipelines

[denscollo]

Fixes #4081

Description

To execute their respective tests, all functional test pipelines test projects must be built and a bot needs to be published as a target. To do so, the pipelines follow a restore, build, publish, and test pattern.

The bot to be deployed project is being built twice, since the build step builds the whole solution, including both the bot to be deployed and the tests projects, and the publish step builds the bot to be deployed as well.

The changes introduced in this branch remove the build steps (including NuGet steps) from all functional test pipelines and reassign building to the publish and test steps for their specific projects, saving approximately 3 minutes on each pipeline execution.

This implementation works best for tests involving a relatively small percentage of projects from a given solution, otherwise, building the whole solution is better since the test task builds all projects found within the specified paths individually.

Specific Changes

• To all functional test and adapter test pipelines:
  • Removes the ci-build-steps.yml template usage. This includes the removal of the Tag build with package version task as the variables involved are not present within these pipelines. We kept the Display env vars for developing/debugging purposes.
  • Adds build configuration parameters to the publish task.
  • Removes parameters --no-build and --no-restore from test task.
  • Adds missing EOL.
• To botbuilder-dotnet-ci-functional-test-windows.yml
  • Updated project path to search exclusively from within the functional tests directory.

Testing

We tested the new implementation for all functional test and adapter tests (besides Twilio) pipelines.
The following images show execution comparisons between the current and the new implementations for one adapter test and a one functional test respectively:

• Slack adapter:
  

• Windows functional test: