avoid hash rate drop during dev pool mining

fix simple start

Since the dev pool is sometimes using another POW than the user pool the
hash date can strongly increase or decrease.
In a case of a hash rate drop a monitoring software could trigger a
wrong miner restart.

- use the hash rate calculated during the user pool mining to
interpulate the number of hashes during the dev pool mining so that the
statistics stay constant.

Simple starts requires always user interactions if config.txt and
pools.txt is not available.
This PR asked the user only on the first advanced option if he/she
preferse the simple start or an advanced mode.
If all parameter are already defined via command line options than the
question will never be shown.

fix execution issue template

update version to 2.10.3

use different issue templates

add issue templates to get more information to solve issues

format all files

- add .clang-format from RYO

This PR removes the space indention by tabs.

AMD: workaround driver memory leaks

simple miner startup

Add the possibility to run a simplified miner configuration.
IN the case the user like to use this mode the number of question to
setup the miner will be reduced to a minimum.

Additional changes:
- add default values for `yes/no` questions

Instead of creating a new kernel for each block we pre-build 25 kernel within a chunk.
This reduces the calls to `clCreateProgramWithSource` which creates the leaks and will crash the miner after a few hours.

Workaround was first introduced by @SChernykh in xmrig-amd

increase version to 2.10.2

OpenCL: fix memory leak

add cli option `amdCacheDir`

add option to control where the amd cache data should be stored

Repair OSX CUDA searched-path for NVRTC

Fix a memory leak that the OpenCL programs was not freed correctly.
First solved by @xmrig

increase version to 2.10.1

cryptonight_r without mediaops

add cryptonight_v8_double

Add support for non media ops for cryptonight_r

fix avx detection

fix cn_gpu rounding mode selection

If cryptonight_gpu is used in the dev pool and a cryptonight_v8 derived
algorithm than cryptonight_gpu will create wrong results if v8 was
running as non ASM version.

Add new algorithm alias for cryptonight_v8_double. The difference to v8
is that the number of iterations is increased.

Add also the currency X-CASH which use cryptonight_double.

CPU: fix cryptonight_r slowdown

If the miner changed the pool (user pool or dev pool) and the network
block of monero has not changed the miner switch to the non asm version.

Add check if the hash function has changed. If the hash function not
point to the asm version the ASM function is recreated.

update currency pow table

remove wrong documentation

The OS is able to disable avx. In that case our avx detection is wrong.
See xmrig issue: https://github.com/xmrig/xmrig/issues/951

Import fix: https://github.com/xmrig/xmrig/commit/6052da3c4399514c95245b2d342f04baa20958db#diff-92fa29935c136762d35981769ac79f52

thx @xmrig for the notification.

fix opencl and cuda cryptonight_r caching

use double hash for cryptonight_r