Add launcher and create tar for trino-gateway

[anilsomisetty]

Description

This pr contains below changes to add launcher script and trino-gateway tar generation similar to trino:

1. New gateway server module to generate gateway tar
2. Creation of launcher scripts from airlift/launcher same as trino
3. Changes to make gateway code compatible with airlift/launcher: config.yml input changed from argument to system variable passed to java command

How to manage the service with new changes:

Command: bin/launcher (run/start/stop/restart/kill/status) --config path_of_config.yml

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

* Fix some things. ({issue}`issuenumber`)

[mosabua]

Not needed.. remove please

[anilsomisetty]

@mosabua I have removed it

[mosabua]

Can you please explain your motivation to add this. Currently the application is a single jar file and a simple Java command .. what benefits do we get from adding a tarball and launcher

[anilsomisetty]

Can you please explain your motivation to add this. Currently the application is a single jar file and a simple Java command .. what benefits do we get from adding a tarball and launcher

@mosabua Below listed things are my motivation which I liked having in trino-gateway similar to trino which was possible with this launcher addition

1. Automated Log Management: With the new launcher, log files (launcher.log and server.log) are automatically generated for the gateway process. This eliminates the need for manual redirection of output to log files, significantly simplifying log management and making it easier to monitor and troubleshoot the gateway.
2. Simplified Execution: The launcher script encapsulates Java commands, simplifying the execution of the application. It ensures that the application is started with the correct JVM options which can be specified in the jvm.config file, environment variables, and classpath settings.
3. Structured Configuration: The launcher provides a structured way to organize the application's configuration and dependencies. Configurations can be placed under the etc directory, libraries under the lib directory, and launcher scripts under the bin directory. This organization enhances clarity and manageability, making it easier to locate and modify configurations and dependencies as needed.
4. Consolidated Packaging: With the addition of multiple files due to the launcher, creating a tarball ensures that all necessary components are packaged together in a single, cohesive archive.

[mosabua]

We will need to add some documentation and upgrade the existing documentation .. I think to merge this we will want to no longer have documentation for the old jar use .. at least not documented.. and the docker image build has to be updated as well. Not sure if we should do this all in one PR or in separate steps .. thoughts @anilsomisetty @oneonestar @vishalya @willmostly @Chaho12 ?

[Chaho12]

I don't mind changing at once as long as we have sufficient documentations as it is BREAKING change.

[anilsomisetty]

@mosabua @Chaho12 Please let me know if you want me to make below changes in current pr:

1. Existing documentation update with latest changes
2. Updates to docker image

[mosabua]

If you are able to work on the docker image, the docs updates, and also the quickstart and other assets. If we go for the tarball it should be a full switch over .. and ideally in one PR to ensure it all changes within one release.

[mosabua]

Please change the module name and hence also the binary and more to trino-gateway-server .. that makes it consistent with trino itself.