Add Schedule parameter to Publish-PerTenantExtensionApps (#3401)

suggestion to add a schedule parameter to allow deployment of the app to
the next major version via CI/CD Pipeline

---------

Co-authored-by: Freddy Kristiansen <freddy.kristiansen@microsoft.com>

ReleaseNotes.txt

@@ -3,6 +3,7 @@ Issue 3613 aka.ms/getbc fallback to NAVUserPassword because token expired when s
 Issue #3617 Regression File Newtonsoft.Json.dll not found when copying item for New-BcCompilerFolder
 Remove functions for supporting Alpaca and Cloud Containers - integration between alpaca and cloud containers with AL-Go for GitHub will NOT be done through BcContainerHelper
 Issue #2623 New-BcContainer for BC25.1 or BC26 insider with includeTestToolkit AI Test Toolkit dependency missing
+Add Schedule parameter to Publish-PerTenantExtensionApps
 
 6.0.20
 Add trustServerCertificate is the parameter exists in various functions that might be running on the host

Saas/Publish-PerTenantExtensionApps.ps1

@@ -42,6 +42,8 @@ function Publish-PerTenantExtensionApps {
         $appFiles,
         [ValidateSet('Add','Force')]
         [string] $schemaSyncMode = 'Add',
+        [ValidateSet('','Current version','Next minor version','Next major version')]
+        [string] $schedule = '',
         [switch] $useNewLine,
         [switch] $hideInstalledExtensionsOutput
     )
@@ -119,6 +121,11 @@ try {
                 throw 'SchemaSyncMode Force is not supported before version 21.2'
             }
         }
+
+        if($schedule) {
+            $body."schedule" = $schedule
+        }
+
         $ifMatchHeader = @{ "If-Match" = '*'}
         $jsonHeader = @{ "Content-Type" = 'application/json'}
         $streamHeader = @{ "Content-Type" = 'application/octet-stream'}