windows launch scripts

[colinsurprenant]

fixes #8126

This is mostly a rewrite of the windows launching batch files, inspired by the ES windows launch batch files.

The initial goal was to add support for the config/jvm.options in its default location or in --path.settings if specified on the command line.

Here are the differences from the linux launching logic:

• existing JAVA_OPTS env var is now ignored, ES is also doing this
• JAVA_TOOL_OPTIONS env var is cleared, ES is also doing this
• now only LS_JAVA_OPTS env var is supported to append options to parsed options in the jvm.options file.
• to simplify the rewrite I dropped the support of the USE_RUBY and USE_DRIP env vars. These were meant for development purposes and are not used anymore I believe.

This also includes a fix in runner.rb which was creating an invalid URI for the path specified for --path.settings command line option.

[untergeek]

I will test this in my Windows 10 environment when I get a chance

[jordansissel]

Tested on Windows 10 - bin/logstash -e 'input { stdin { } }' works.

I uncommented a few arbitrary things in config/jvm.options and ran logstash -- all working :)

[colinsurprenant]

merged into master, 6.x, 6.0, 5.6