Fix: use a ms granularity seed to avoid same random numbers

[ianfhunter]

Description

Partially fixes: #292

• clock() uses a ms granularity, rather than a second one

Outstanding Issue:
It still uses rand() however, which is cryptographically insecure.

Considering PCG for longer term solution or Mersenne Twist

How Has This Been Tested

for x in 1 2 3 4 5
do
    ./build/dice d100
done

Before

52;
52;
52;
52;
52;

After

58;
26;
85;
14;
96;

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Test Coverage (Additional test(s) without any extra code)
• Documentation Improvements
• Code Quality / Maintenance

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation & I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I give my permission for my code to be used in this project under this license and any future license terms