ci(manager): update manager version to upgrade from to 3.3

Since new Manager version 3.4 is about to be released, upgrade
pipelines should be adjusted to run upgrade from version 3.3.*
instead of 3.2.*

jenkins-pipelines/manager/debian11-manager-upgrade.jenkinsfile

@@ -9,7 +9,7 @@ managerPipeline(
 
     target_manager_version: 'master_latest',
 
-    manager_version: '3.2',
+    manager_version: '3.3',
 
     test_name: 'mgmt_upgrade_test.ManagerUpgradeTest.test_upgrade',
     test_config: '''["test-cases/upgrades/manager-upgrade.yaml", "configurations/manager/debian11.yaml"]''',

jenkins-pipelines/manager/ubuntu20-manager-upgrade.jenkinsfile

@@ -10,7 +10,7 @@ managerPipeline(
     target_manager_version: 'master_latest',
 
     // Upgrade from previous minor release (the first one)
-    manager_version: '3.2.0',
+    manager_version: '3.3.0',
 
     test_name: 'mgmt_upgrade_test.ManagerUpgradeTest.test_upgrade',
     test_config: '''["test-cases/upgrades/manager-upgrade.yaml", "configurations/manager/ubuntu20.yaml"]''',

jenkins-pipelines/manager/ubuntu22-manager-older-enterprise-upgrade.jenkinsfile

@@ -11,7 +11,7 @@ managerPipeline(
 
     target_manager_version: 'master_latest',
 
-    manager_version: '3.2',
+    manager_version: '3.3',
 
     test_name: 'mgmt_upgrade_test.ManagerUpgradeTest.test_upgrade',
     test_config: 'test-cases/upgrades/manager-upgrade.yaml',

jenkins-pipelines/manager/ubuntu22-manager-upgrade.jenkinsfile

@@ -9,8 +9,8 @@ managerPipeline(
 
     target_manager_version: 'master_latest',
 
-    // Upgrade from previous minor release (the last one), for this specific case it'd be 3.2.8
-    manager_version: '3.2',
+    // Upgrade from previous minor release (the last one), for this specific case it'd be 3.3.3
+    manager_version: '3.3',
 
     test_name: 'mgmt_upgrade_test.ManagerUpgradeTest.test_upgrade',
     test_config: 'test-cases/upgrades/manager-upgrade.yaml',