Make jar extraction multi-process safe

[IlyaMuravjov]

Description

Sometimes either under heavy loud or when running UtBot in IDE and via tests in parallel, UtBot may crush because its own jars are locked by other processes, to avoid that this PR lets UtBot dynamically change locations to which it extracts jars.

How to test

Manual tests

• Open ../Temp/UTBot/utbot-instrumentation/0/utbot-instrumentation-shadow.jar with any program (e.g. run ping google.com -t < utbot-instrumentation-shadow.jar on Windows)
• Ensure you can't delete utbot-instrumentation-shadow.jar manually anymore
• Recompile utbot (make sure compilation takes place after the previous step and output isn't cached)
• Generate unit test for any method

UtBot should recognise that it can't update ../Temp/UTBot/utbot-instrumentation/0/utbot-instrumentation-shadow.jar and extract new instrumentation jar to ../Temp/UTBot/utbot-instrumentation/1/utbot-instrumentation-shadow.jar.

Self-check list

• I've set the proper labels for my PR (at least, for category and component).
• PR title and description are clear and intelligible.
• I've added enough comments to my code, particularly in hard-to-understand areas.
• The functionality I've repaired, changed or added is covered with automated tests.
• Manual tests have been provided optionally.
• The documentation for the functionality I've been working on is up-to-date.