Make `max` as inclusive for `toBeInRange()` matcher

[mayankshukla94]

Please refer toBeInRange bug in implementation #670 for the details.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 36d612540077eee521585c151d33580e3013ba66

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (711fdcc) 100.00% compared to head (36d6125) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #671   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           73        73           
  Lines          674       674           
  Branches       290       290           
=========================================
  Hits           674       674           

Files	Coverage Δ
src/matchers/toBeInRange.js	100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.