#1386 fix nextInt and nextLong with extreme boundaries

[asolntsev]

e.g.

• randomService.nextInt(Integer.MIN_VALUE, Integer.MAX_VALUE)
• randomService.nextLong(Long.MIN_VALUE, Long.MAX_VALUE)

[codecov]

Codecov Report

Attention: Patch coverage is 86.66667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 92.26%. Comparing base (c94d690) to head (b60ed48).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...main/java/net/datafaker/service/RandomService.java	84.61%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1388      +/-   ##
============================================
- Coverage     92.32%   92.26%   -0.06%     
- Complexity     3152     3154       +2     
============================================
  Files           319      319              
  Lines          6146     6152       +6     
  Branches        592      593       +1     
============================================
+ Hits           5674     5676       +2     
- Misses          331      335       +4     
  Partials        141      141              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kingthorin]

Drop the unrelated workflow change?

[kingthorin]

To be clear I do think that's probably a handy change if you want to submit it separately.

(I'll leave that approval/merge up to bodiam but for my two cents it's good)

[kingthorin]

Ha good catch, one of obviously didn't notice the mismatch.

[asolntsev]

that's probably a handy change if you want to submit it separately

I am not sure if it's useful. I wanted looked for a github action that would generate a readable test report.
Because usually it's hard to find which test failed (when a build fails in Github actions).
But this specific action didn't help a lot.