#2229 was not solving the issues

- revert #2229
- introduce the working fix

The OpenCl version of the blockchain driver is not understanding if
apointer to a pointer points into shared memory and throw an error
during the compilation.

- revert the usage of the struct to group all shared memory arrays

- add more information if a algorithm derives from an other
- update `pools.tpl`

Add seperate kernel to prepare the scratchpad memory.

Optimize the auto adjustment for cn_gpu based on precomputed occupancy
values from CUDA10.

Combine the shared memory for a hash within one struct.
Reduce the shared memory footprint per hash by 64 byte.

- rename variable names like `b` and `bb` to something with a little bit
of meaning.

Optimize cn_gpu

based on the suggestion from @xmrig https://github.com/xmrig/xmrig-amd/commit/db4e169f3a78f273abf89ea8cf5bba7eccf1490b

This PR replaces #2196 and add support for zelerius.

- add cryptonight_v8_half
- re-add stellite and masari to the supported coins

cryptonight_turtle is only cryptonight_v8 with a different scratchpad,
iteration and mask value.
We are using now the new machanism to describe such derived POWs.

A POW is now defined by a function `f` and three degrees of freedom `f(iteration, scratchpad, mask)`.
`f` is the base algorithm like `cryptonight, cryptonight_gpu`
An easy to pars snytax to write the full POW definition down is: `cryptonight_gpu:0x0000c000:0x00200000:0x001fffc0`

This change make it very easy to integrate the new trend of variate the
number of iteations or the scratchpad size without modifying the full
code.

To avoid that a miner is waisting power with there CPU to mine cn_gpu the
auto suggestion will comment out the config.

@xmrig provided the information that the driver 19.2.1 for vega also
create invalid results if pragma unroll is used for the groestl algo.

- use the user defined unroll
- auto suggestion:
  - only tune for cn_gpu if this is the main user
currency (after a fork)
  - set unroll to 1 for cn_gpu

OpenCl kernel using a larger work group size than configured by the
user to increase the occupancy. Depending on the algorithm and device
the size is limited.

This PR fixes that the user was able to select a invalid work group size.

If comp_mode is used the code will not compile.

- fix compile issue
- fix wrong conditions to handle `comp_mode`

During the implementation of `cryptonight_gpu` we missed to add the name
of the algorithm to jpsock.

- add function to translate an algorithm into a name.

Remove `static constexpr` within the global kernel. This is not
supported by all CUDA versions.

- rename `Intense` to `Lethean`
- remove `masari` and `stellite`, both hase forked to a currently
unsupported algorithm

Windows driver creates wrong code if unroll is used.

Fix message with the maximal allowed worksize if cryptonight_gpu is
used.

optimize the algorithm for cryptonight_gpu autosuggestion

switch with block 6 to cryptonigh_gpu
(https://github.com/ryo-currency/ryo-currency/blob/7bc5dc40864e518753807d04c17d617f728da156/src/cryptonote_config.h#L185)

psychocrypt committed 9 minutes ago
 - use precomuted indicies within the loop
 - `cn_explode_gpu` use all threads to load the state

Use the algorithm names from `cryptonight.hpp` instead if number within the OpenCL kernel.

- fix race condition during shared memory access
- optimize memory access

- fix broken trutle coin
- fix non cn_gpu algorithms

Co-authored-by: psychocrypt <psychocryptHPC@gmail.com>
Co-authored-by: fireice-uk <fireice-uk@users.noreply.github.com>

Avoid that we do multiple lookups to `std::map` to find the OpenCL
kernel binaries.

- add helper method `GetAllAlgorithms()` to get all active POW
algorithms
- select max scratchpad memory size based on the dev pool and user
algorithms

In the current implementation the POW algorithm in dev pool section of a
currency will not be taken into account during the binary creation.
This PR changes the behavior and allow to create binaries for more than two POW algorihms.