Attempt to make crate-testing work under windows

[mackerl]

• handle child process exits
• handle temporary file locks
• different urls for windows and linux
• upgrade cratedb tested version as 3.x is not released as zip
• no latest test as there is no latest download link for windows
• TODO: few fixes left, but don't know how at the moment
• TODO: cannot upload large files in src/test/resources - locally I had there the 6.1.1 for windows and not windows

Summary of the changes / Why this is an improvement

Checklist

• Link to issue this PR refers to (if applicable): Fixes #???

[mackerl]

I came quite far with supporting windows, altough its a pain :) (files access, child processes ...)
However now I face some limitations ... I cannot upload huge zips, tar.gz to fork in lfs mode as I am not the branch owner
I failed to fix some tests as I lack there knowledge whats happening in crate.

[amotl]

I came quite far with supporting windows, altough its a pain :) (files access, child processes ...)

Hi Mario. Thanks a stack for your contribution. I experienced similar pains like you when trying to manage the CrateDB process lifecycle on Windows the other day in Python lands at mfussenegger/cr8#337. ¹

Footnotes

1. In order not to hijack the discussion on this PR, I've elaborated about it in Support for testing on Windows #93, also to explore the problem domain beyond crate-java-testing, looking at potential solutions around using container technologies instead of manual process management. ↩

[matriv]

Thx @mackerl I will take a look in the next days.