build: pass branding into the nuget variable template (#16122)

This fixes a cosmetic issue with the version number in the unpackaged
builds and NuGet packages.

They were showing up as `-preview`, even when they were stable, because
the variable template didn't know about the branding.

Author: DHowett

build/pipelines/ob-nightly.yml

@@ -18,6 +18,8 @@ name: $(BuildDefinitionName)_$(date:yyMM).$(date:dd)$(rev:rrr)
 
 variables:
   - template: templates-v2/variables-nuget-package-version.yml
+    parameters:
+      branding: Canary
   - template: templates-v2/variables-onebranch-config.yml
 
 extends:

build/pipelines/ob-release.yml

@@ -62,6 +62,8 @@ name: $(BuildDefinitionName)_$(date:yyMM).$(date:dd)$(rev:rrr)
 
 variables:
   - template: templates-v2/variables-nuget-package-version.yml
+    parameters:
+      branding: ${{ parameters.branding }}
   - template: templates-v2/variables-onebranch-config.yml
 
 extends:

build/pipelines/templates-v2/pipeline-full-release-build.yml

@@ -62,6 +62,8 @@ parameters:
 
 variables:
   - template: variables-nuget-package-version.yml
+    parameters:
+      branding: ${{ parameters.branding }}
 
 resources:
   repositories:

build/pipelines/templates-v2/variables-nuget-package-version.yml

@@ -1,3 +1,7 @@
+parameters:
+  - name: branding
+    type: string
+
 variables:
   # If we are building a branch called "release-*", change the NuGet suffix
   # to "preview". If we don't do that, XES will set the suffix to "release1"