File name encoding validation task works incorrectly when Bamboo started by systemctl

Issue Summary

If Bamboo configured as systemctl service then validation task FileNameEncodingIsReasonable fails with misleading message

Steps to Reproduce

1. Configure Bamboo service for systemctl
2. Start Bamboo

Expected Results

Task 51210 : Verify file name encoding (bootstrap) passes

Actual Results

The below log message:

2020-06-30 06:24:57,773 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] 51210 : Verify file name encoding (bootstrap)
2020-06-30 06:24:57,773 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] ---------------------------------------------
2020-06-30 06:24:57,776 WARN [localhost-startStop-1] [FileNameEncodingIsReasonable] Encoding [Cp1252] used to encode file names is not capable of handling extended character sets. You may encounter failures during artifact transfers.

Workaround

1. Make sure that Bamboo is configured with UTF-8 encoding by configuring the following JVM options:

   -Dsun.jnu.encoding=UTF-8
   -Dfile.encoding=UTF-8
   

   Configuring your system properties

2. Disable validation task by commenting the following line in the file <bamboo-install>/atlassian-bamboo/WEB-INF/classes/upgrade.xml:

       <!--<upgrade build="51210" build-min="0" build-max="999999"
                class="com.atlassian.bamboo.upgrade.tasks.validation.FileNameEncodingIsReasonable"/>-->