The login result of a pool contains the first job for the miner.
In the case where the pool is sending very fast after the pool login result
a new job it is possible that the newer job is processed faster than the job within the login result.
The result will be that the miner is mining an older job instead the newest (last received).

- enumerate all received messages
- trace the message id of the last procssed job
- skip all jobs where the message id is older than the last procesed id

ignore duplicated equal job from pools

Some pools or proxys are sending multiple times in row the same job to the miner.
This PR will extent the miner to trigger an socket error if job with the same `jobID` than the current active job is received.

Move motd evaluation before the possibil part where a job is ignored.

fix possible race condition in jpsock

Fix condition on stellite check

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

set correct `iPoolId` for miner_work

Add masari coin 

- initialize miner_work iPoolId in the default constructor with the invalid pool id
- move definition of `pool_data` into an own file

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);
```