Don't record own computor's duplicated invalid nonce.

[cyber-pc]

This PR fix unvalidated solutions recorded in system.solutions on duplicate submission.

In processTickTransactionSolution, when minerSolutionFlags detects a duplicate (publicKey, miningSeed, nonce), the else branch skips scoring but still records into system.solutions[] if the entry doesn't exist. This allows invalid solutions (rejected on first submission) to be recorded on second submission without any score check.
This bug is limited to the node's own F2 display and solution publication, minerScores are unaffected.

Fix: remove the unconditional add new entry block from the duplicate path. The existing dedup search and SOLUTION_RECORDED_FLAG marking for legitimate entries is preserved.

[krypdkat]

we should run the score again and continue the original flow if score is valid:

        unsigned int solutionScore = (*::score)(processorNumber, transaction->sourcePublicKey, transaction->miningSeed, transaction->nonce);
        score_engine::AlgoType selectedAlgo = score_engine::getAlgoType(transaction->nonce.m256i_u8);
        if (score->isValidScore(solutionScore, selectedAlgo))
        {
            resourceTestingDigest ^= solutionScore;
            KangarooTwelve(&resourceTestingDigest, sizeof(resourceTestingDigest), &resourceTestingDigest, sizeof(resourceTestingDigest));
            const int threshold = (system.epoch < MAX_NUMBER_EPOCH) ?
                solutionThreshold[system.epoch][selectedAlgo]
                : score_engine::DEFAUL_SOLUTION_THRESHOLD[selectedAlgo];
            if (score->isGoodScore(solutionScore, threshold, selectedAlgo)) 
            .....

there is (rare) chance that 2 solutions has the same flag.
score engine has cache system, it will not cost any performance.

[cyber-pc]

We will delay this PR for next epoch, I will need to test to make sure it work as expectation.