Container entrypoint script should pass arguments

[MalteHei]

Is your feature request related to a problem? Please describe.
When starting CloudBeaver in a container, any arguments provided are ignored by the entrypoint. This is frustrating when your environment differs from the expected default.
In my case, for example, I'd like to mount the main cloudbeaver.conf in /config/ and thus pass -web-config /config/cloudbeaver.conf as an argument to the container, as described in the wiki.

Describe the solution you'd like
The container entrypoint launch-product.sh just ignores any argument, while run-cloudbeaver-server.sh passes them to the java command.
I expect the entrypoint to do the same.

Describe alternatives you've considered
I've considered overriding the entrypoint to be run-cloudbeaver-server.sh which should work because I don't run the container as root. Though I prefer not overriding the default entrypoint for any image.
I also wonder if there is an environment variable that can be used as an alternative to -web-config?

[MalteHei]

Also, while trying to implement a fix for this, I noticed that when running run-cloudbeaver-server.sh -web-config /foo.conf, the app still tries to load /opt/cloudbeaver/conf/cloudbeaver.conf.

The reason for this seems to be that the script sets -web-config before custom arguments are passed.

[dariamarutkina]

Hello, @MalteHei!

Thanks for the suggestion! We appreciate your detailed investigation. We will consider this improvement and plan to implement it in the near future🦫