Upgrade to 2021.4 fails

[Akaizoku]

Issue

Upgrading from a previous version to 2021.4 fails.

Description

When upgrading from 2021.3 or an older version to 2021.4, the upgrade script throws an error after the backup of the database while attempting to restart the service.

yyyy-MM-dd hh:mm:ss	CHECK	Starting Alteryx Server upgrade to 2021.4.1.06380
yyyy-MM-dd hh:mm:ss	INFO	Retrieving current version
yyyy-MM-dd hh:mm:ss	CHECK	Start full backup of Alteryx Server
yyyy-MM-dd hh:mm:ss	INFO	Check Alteryx Service status
yyyy-MM-dd hh:mm:ss	INFO	Stopping Alteryx Service                      
yyyy-MM-dd hh:mm:ss	CHECK	Alteryx Service successfully stopped
yyyy-MM-dd hh:mm:ss	INFO	Create MongoDB database backup
yyyy-MM-dd hh:mm:ss	INFO	Backup configuration files
yyyy-MM-dd hh:mm:ss	WARN	SystemAlias configuration file could not be found
yyyy-MM-dd hh:mm:ss	WARN	SystemConnections configuration file could not be found
yyyy-MM-dd hh:mm:ss	INFO	Backup controller token
yyyy-MM-dd hh:mm:ss	INFO	Compress backup files
yyyy-MM-dd hh:mm:ss	INFO	Remove staging backup folder
yyyy-MM-dd hh:mm:ss	INFO	Starting Alteryx Service                    
yyyy-MM-dd hh:mm:ss	ERROR	Alteryx Service could not be started

Cause

This is due to two factors:

1. The AlteryxService.exe utility exit code when starting the Alteryx Service has changed between version 2021.3 and 2021.4.

   Version	Success exit code
   2021.3	2
   2021.4	0

2. The backup triggered during the upgrade references the target version instead of the old one, which fails to pass the version check built to prevent the issue described above.

[Akaizoku]

Fixed by pull request #3.