Trigger event with a new job after the current pool job is updated.

Add masari coin 

Spell check

support stellite v4 fork

solve #1494

- add algorithm `cryptonight_v7_stellite` (internal named: `cryptonight_stellite`)

fix that cli option `--noAMDCache`

Small typo correction

rename printed algorithms

add support for IPBC coin

changes printed algorithm names to algorithms exposed to the used instead of internal used names

- add algorithm `cryptonight_lite_v7_xor`
- update documentation

- fix that to much OpenCL calls whre used if cache is disabled

Add turtlecoin as a config option

Fixes #1467

version update to 2.4.3

BBSCoin support and get ready for cryptonight v7 upgrade

CUDA 8 deprecation warning silencer

Update ITNS with v4 fork to CN v1

- fix dev pool algorithms
- add note to `pools.tpl`
- remove pool suggestion

Official Announcement: https://intensecoin.com/2018/04/16/imminent-hard-fork-and-network-attack/

fix wrong unique_lock usage

Use EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH

clang warns about the wrong usage:
```
```
xmrstak/net/jpsock.cpp:232:30: warning: parentheses were disambiguated as redundant parentheses around declaration of variable named 'job_mutex' [-Wvexing-parse]
        std::unique_lock<std::mutex>(job_mutex);
                                    ^~~~~~~~~~~
xmrstak/net/jpsock.cpp:232:30: note: add a variable name to declare a 'std::unique_lock<std::mutex>' initialized with 'job_mutex'
        std::unique_lock<std::mutex>(job_mutex);
```

fix wrong algo selection

Use EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH to control the path to which the executable and libraries are installed.

remove fork version for sumokoin and monero7

Dev

- allow the dev pool to fork on a different block version than the user descriped coin

All algorithm are centered around the user coin description.
It is allowed to have two two different coin algorithms in the user coin description.
It is only allowed to use algorithms for the dev pool coin description those are used in the user coin description.
There are two ways to define a non forking coin.
  - set both user coin algorithm descriptions to the same algorithm and set version to zero
  - set the first algorithm in the user coin description to something you like to use in the dev pool
    and set the second algorithm to the correct representation of the coin. Set the version to 255.
    This will allow that the dev pool can mine on a different coin algorithm than the not forking user coin.
    Do not use an algorithm with different scratchpad size for the dev pool.

In the case where the dev pool mines on a higher version than a monero fork coin the miner is not resetting the algorithm.
This PR select the correct algorithm each time the block version hash changed.