feat(datatype): introduce probability option to boolean

[ST-DDT]

Throughout our code base the have some locations that use probabilities to decide what to do.
This PR merges these occurrences into our datatype.boolean() method and thus provides this option to others.

Docs Preview

[codecov]

Codecov Report

Merging #1476 (4825329) into next (4204a6a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #1476   +/-   ##
=======================================
  Coverage   99.63%   99.64%           
=======================================
  Files        2175     2175           
  Lines      237613   237636   +23     
  Branches     1009     1013    +4     
=======================================
+ Hits       236751   236782   +31     
+ Misses        841      833    -8     
  Partials       21       21           

Impacted Files	Coverage Δ
src/modules/datatype/index.ts	99.18% <100.00%> (+0.05%)	⬆️
src/modules/finance/index.ts	100.00% <100.00%> (ø)
src/modules/helpers/index.ts	98.44% <100.00%> (-0.01%)	⬇️
src/modules/internet/user-agent.ts	92.59% <0.00%> (+2.11%)	⬆️

[Shinigami92]

Looking into the test snapshots, it looks like the behavior exactly swapped, true is now false and false is now true 🤔
Should we just switch the condition to archive the "old" result(s)?

[ST-DDT]

Looking into the test snapshots, it looks like the behavior exactly swapped, true is now false and false is now true 🤔 Should we just switch the condition to archive the "old" result(s)?

IMO the probability should refer to true and not false. I dont know how to preserve the old behavior that wouldn't result in bad code readability/understandability.
E.g. 1 - float(...) < probability.
Its a major version upgrade so a predictably flipped random boolean is acceptable IMO.
Also, if we flip the result, then we would have to flip the usages as well (maybe+iban).