expect: Add matcher `toBeInRange()` to validate if array elements are within the specified range

[mayankshukla94]

What

In this PR, I have created a new matcher toBeInRange.

Why

Recently, I came across a use case where I had to validate if Year dropdown has options within the specified range. When I checked for assertions, then no such assertion found where I can specify the range and validate or assert.

Notes

Housekeeping

• [x] Unit tests
• [x] Documentation is up to date
• [x] No additional lint warnings
• [x] Typescript definitions are added/updated where relevant

[SimenB]

@keeganwitt @mattphillips thoughts?

[codecov[bot]]

Codecov Report

Merging #461 (2d7adc5) into main (bbbe109) will not change coverage. The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #461   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           72        73    +1     
  Lines          594       601    +7     
  Branches       151       153    +2     
=========================================
+ Hits           594       601    +7     

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

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[mayankshukla94]

@keeganwitt @mattphillips thoughts?

@keeganwitt @mattphillips Could you please provide your input?

[keeganwitt]

This seems reasonable to me. We could make the inclusive vs exclusive more flexible, but I don't think that'd add much value, and being inclusive is what I'd kinda expect.

[keeganwitt]

Also add this matcher to the README.

[mayankshukla94]

@mattphillips Thank you for the detailed review. I have made the changes. Please review again.

[mayankshukla94]

Hello @keeganwitt @mattphillips,

Could you please review this again?

Thanks!

[mayankshukla94]

@mattphillips @keeganwitt I have resolved the conflicts. Please have a look again.

[mayankshukla94]

Hello @SimenB @keeganwitt @mattphillips

Any update on this?

[keeganwitt]

Sorry, I haven't had a chance to get back to this. I'll take a look this week.

[keeganwitt]

A few more things are needed before this is ready:

1. https://github.com/jest-community/jest-extended/blob/main/website/docs/matchers/index.md should be updated to include this new matcher.
2. There are two places in index.d.ts that get updated every time a new matcher is added: the Matchers interface and Expect interface. This PR only has the latter.

[mayankshukla94]

A few more things are needed before this is ready:

1. https://github.com/jest-community/jest-extended/blob/main/website/docs/matchers/index.md should be updated to include this new matcher.
2. There are two places in index.d.ts that get updated every time a new matcher is added: the Matchers interface and Expect interface. This PR only has the latter.

Sure will update.

[keeganwitt]

A few more things are needed before this is ready:

1. https://github.com/jest-community/jest-extended/blob/main/website/docs/matchers/index.md should be updated to include this new matcher.
2. There are two places in index.d.ts that get updated every time a new matcher is added: the Matchers interface and Expect interface. This PR only has the latter.

Sure will update.

Sounds good! Thanks for your persistence!

[mayankshukla94]

@keeganwitt I have updated now. Please review