Bitbucket installer fails to create service on RHEL 9.3

Issue Summary

Installing Bitbucket on RHEL 9.3 fails with the following error in the installation log:

[ERROR] com.install4j.runtime.beans.actions.misc.RunExecutableAction [ID 79562]: executable does not exist: /etc/init.d/atlbitbucket
        Execute action not successful after 0 ms
[INFO] com.install4j.runtime.beans.actions.control.RunScriptAction [ID 59785]: Execute action
       Property rollbackScript: null
       Property script: com.install4j.script.I4jScript_Internal_115
       Property rollbackSupported: false
       Waiting 180 seconds for the application to come up with a polling interval of 10 seconds
       Failed to connect to http://localhost:7990/status. Waiting for application to come up
       (+17)
       Variable changed: app.launch.error=true[class java.lang.Boolean]
       Application did not come up after 180 seconds
[ERROR] com.install4j.runtime.beans.actions.control.RunScriptAction [ID 59785]: Execute action not successful after 180127 ms

The installer output will also write this:

The installer was unable to detect whether Bitbucket started correctly
Please consult the ' /absolute/path/to/bitbucket-home/log/atlassian-bitbucket.log' file to verify that Bitbucket started successfully

Steps to Reproduce

1. Run the Bitbucket installer on RHEL 9.3
2. In the last step, the installer will ask if you'd launch Bitbucket. If you agree, after a while, the following output is provided:

   The installer was unable to detect whether Bitbucket started correctly
   Please consult the ' /absolute/path/to/bitbucket-home/log/atlassian-bitbucket.log' file to verify that Bitbucket started successfully
   

1. Check the installer log in order to see the service installation error.

Actual Results

The service is not created and the instance does not start when the installer finishes.

According to the installer log, the /etc/init.d/atlbitbucket executable does not exist, and it happens to be so because RHEL 9.3 is a systemd-based OS where traditional init scripts have been replaced by native systemd services files, so /etc/init.d no longer exists or should no longer be used.

Expected Results

The Linux service is created as systemd service and the service is able to start when the installer finishes.

Workaround

Follow the steps from Run Bitbucket as a Linux service - Using a systemd unit file in order to manually install the Bitbucket service after the installer finishes, or start Bitbucket manually without a service.