Improve String-to-Number Conversion Logic in Seed Handling

[allquantor]

This Pull Request introduces an optimized and potentially more collision-resistant string-to-number conversion method in the seed-handling logic.

Before:
With the current logic, different string seeds might result in the same numeric seed if the sum of their character codes is the same. For example:

"AB" would be converted to 138 because 'A' has a character code of 65, ' B' has a character code of 66, and 65 + 66 + 1 (the initial accumulator value) is 132.
"BA" would also be converted to 132 for the same reason.

Example:

const seed = "BA"; // Try changing this to "AB" and you'll get the same result
const numberFromString = seed.split('').reduce((acc, curr) => acc + curr.charCodeAt(0), 1);
const numericSeed = Math.floor(Number(numberFromString));
console.log(numericSeed); // Output: 132

Now:
A straightforward improvement to the hashing function enhances its capacity to disperse different input strings to a broader range of output values, thus reducing collisions.

[alekmeckaroski]

@andreasonny83
Is this PR merging?
I am using this library for generating names and I am using unique strings as seed.
Although I am working with large number of seeds, inevitably coming to a collision I want to make them minimal.
Please review the code and merge it so I can update.

Thanks

[andreasonny83]

@alekmeckaroski
Please make sure to update the tests and write new use cases for covering the change introduced