Eliminate generation of config files multiple times in the integration test pipelines (#1910)

## Why make this change?

- Closes #1909 
- To include CLI as part of the integration testing, config file used
for all the integration tests are generated by CLI and in turn, these
generated config files are used by the tests. The config file generation
is added as a post build event (in the CLI module) to enable generation
of config files in the a) integration testing pipelines b) local (if
developer wishes to try out the config files we've used during
development/testing.)
- At the moment, the config file generation gets triggered twice.
Ensuring that the config file generation is executed only once will
improve the time taken in the integration testing pipelines.

## What is this change?

- The config file generation gets triggered when building the 1) CLI 2)
CLI.Tests modules.
- The build step in the pipeline is broken up as two

1. Build all the non-testing modules with
`-p:generateConfigFileForDbType=<database_type>`
2. Build the test modules without any arguements. The presence of
`-p:generateConfigFileForDbType` argument determines the execution of
config generation script. So, when the test modules are built without
this argument, the config file generation script does not execute.

## Choice of the executing config generation script in CLI vs CLI.Tests
module:

The PostBuildEvent for executing the config generator scripts after
build could have been added either in `CLI` or `CLI.Tests` module. The
module where this event is added determines where the
`generateConfigFileForDbType` is used along with the `dotnet build`
command.

From the perspective of being able to execute the integration tests,
there is no difference in adding it in CLI or CLI.Tests module.

Adding it in CLI project has the additional advantages: 

1) When a developer wishes to clone the repo and work with the config
files we have used thus far for development/testing, being able to
execute this post build event using the `-p:generateConfigFileForDbType`
enables them to do this. Test module does not seem to be the right place
for this.
2) Being able to validate new changes being worked on manually in local
- For these, typically the test modules are not built. For example: When
a change spans CLI + Engine modules, being able to generate the config
file and validate that the introduced changes work fine is essential.
One should be able to perform this manual validation just by building
the modules where the changes are there without requiring building the
test projects.

## How was this tested?

- [x] Executing integration tests in the pipeline manually. Also, in the
pipelines that have executed for this PR, it can be seen that the config
generation executed only once in the integration testing pipelines.


## Sample Request(s)

N/A

Author: severussundar

.pipelines/cosmos-pipelines.yml

@@ -60,9 +60,18 @@ steps:
   displayName: Build
   inputs:
     command: build
-    projects: '**/*.csproj'
+    projects: |
+        **/*.csproj
+        !**/*Tests*.csproj
     arguments: '-p:generateConfigFileForDbType=cosmosdb_nosql --configuration $(buildConfiguration)' # Update this to match your need
 
+- task: DotNetCoreCLI@2
+  displayName: Build Test Projects
+  inputs:
+    command: build
+    projects: '**/*Tests/*.csproj'
+    arguments: '--configuration $(buildConfiguration)'
+
 - bash: |
     echo "Waiting for CosmosDB Emulator to Start"
     until [ "$(curl -k -s --connect-timeout 5 -o /dev/null -w "%{http_code}" https://localhost:8081/_explorer/index.html)" == "200" ]; do

.pipelines/dwsql-pipelines.yml

@@ -79,9 +79,18 @@ jobs:
     displayName: Build
     inputs:
       command: build
-      projects: '**/*.csproj'
+      projects: |
+        **/*.csproj
+        !**/*Tests*.csproj
       arguments: '-p:generateConfigFileForDbType=dwsql --configuration $(buildConfiguration)' # Update this to match your need
 
+  - task: DotNetCoreCLI@2
+    displayName: Build Test Projects
+    inputs:
+      command: build
+      projects: '**/*Tests/*.csproj'
+      arguments: '--configuration $(buildConfiguration)'
+
   - task: [email protected]
     displayName: 'Generate dab-config.DwSql.json'
     inputs:
@@ -194,9 +203,18 @@ jobs:
     displayName: Build
     inputs:
       command: build
-      projects: '**/*.csproj'
+      projects: |
+        **/*.csproj
+        !**/*Tests*.csproj
       arguments: '-p:generateConfigFileForDbType=DwSql --configuration $(buildConfiguration)' # Update this to match your need
-    
+
+  - task: DotNetCoreCLI@2
+    displayName: Build Test Projects
+    inputs:
+      command: build
+      projects: '**/*Tests/*.csproj'
+      arguments: '--configuration $(buildConfiguration)'
+
   - task: [email protected]
     displayName: 'Generate dab-config.DwSql.json'
     inputs:

.pipelines/mssql-pipelines.yml

@@ -61,9 +61,18 @@ jobs:
     displayName: Build
     inputs:
       command: build
-      projects: '**/*.csproj'
+      projects: |
+        **/*.csproj
+        !**/*Tests*.csproj
       arguments: '-p:generateConfigFileForDbType=mssql --configuration $(buildConfiguration)' # Update this to match your need
 
+  - task: DotNetCoreCLI@2
+    displayName: Build Test Projects
+    inputs:
+      command: build
+      projects: '**/*Tests/*.csproj'
+      arguments: '--configuration $(buildConfiguration)'
+
   - task: [email protected]
     displayName: 'Generate dab-config.MsSql.json'
     inputs:
@@ -176,9 +185,18 @@ jobs:
     displayName: Build
     inputs:
       command: build
-      projects: '**/*.csproj'
+      projects: |
+        **/*.csproj
+        !**/*Tests*.csproj
       arguments: '-p:generateConfigFileForDbType=MsSql --configuration $(buildConfiguration)' # Update this to match your need
-    
+  
+  - task: DotNetCoreCLI@2
+    displayName: Build Test Projects
+    inputs:
+      command: build
+      projects: '**/*Tests/*.csproj'
+      arguments: '--configuration $(buildConfiguration)'
+
   - task: [email protected]
     displayName: 'Generate dab-config.MsSql.json'
     inputs:

.pipelines/mysql-pipelines.yml

@@ -60,9 +60,18 @@ jobs:
     displayName: Build
     inputs:
       command: build
-      projects: '**/*.csproj'
+      projects: |
+        **/*.csproj
+        !**/*Tests*.csproj
       arguments: '-p:generateConfigFileForDbType=mysql --configuration $(buildConfiguration)' # Update this to match your need
 
+  - task: DotNetCoreCLI@2
+    displayName: Build Test Projects
+    inputs:
+      command: build
+      projects: '**/*Tests/*.csproj'
+      arguments: '--configuration $(buildConfiguration)'
+
   - task: [email protected]
     displayName: 'Generate dab-config.MySql.json'
     inputs:

.pipelines/pg-pipelines.yml

@@ -55,9 +55,18 @@ jobs:
     displayName: Build
     inputs:
       command: build
-      projects: '**/*.csproj'
+      projects: |
+        **/*.csproj
+        !**/*Tests*.csproj
       arguments: '-p:generateConfigFileForDbType=postgresql --configuration $(buildConfiguration)' # Update this to match your need
 
+  - task: DotNetCoreCLI@2
+    displayName: Build Test Projects
+    inputs:
+      command: build
+      projects: '**/*Tests/*.csproj'
+      arguments: '--configuration $(buildConfiguration)'
+
   - task: [email protected]
     displayName: 'Generate dab-config.PostgreSql.json'
     inputs: