WINDOWS_SERVICE_STOP_TIMEOUT not used in stop command for Windows Service

[jimblye]

Describe the bug
On Windows, there is a 'server registerWinService <SERVER_NAME>' command that adds the Liberty server to the registry along with commands to start and stop the server. The stop command is not using the --timeout option, which means it always uses the default timeout of 30 seconds. For Windows services the timeout is supposed to be defined by the variable WINDOWS_SERVICE_STOP_TIMEOUT.

Steps to Reproduce
Enter the 'server registerWinService' command and then check the registry location to see the stop command parameters:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\defaultServer\Parameters

Expected behavior
The stop command should include parameters --stoptimeout WINDOWS_SERVICE_STOP_TIMEOUT.
It does not.

Diagnostic information:

• Windows ONLY (and only when running Liberty as a Windows Service)
• OpenLiberty Version: [e.g. 21.0.0.11 - 25.0.0.1]
• Affected feature(s) : none
• Java Version: all
• server.xml configuration N/A

Additional context
The same applies to the start command, but that is a separate issue, and is more of a problem, because there is no --timeout for the start command. That option will need to be added.