fix: select next if we are at the of the current segment

[dzianis-dashkevich]

Description

Assume we have the following playlist:

#EXTINF:6.000,
segment-1.ts
#EXTINF:6.000,
segment-2.ts
#EXTINF:6.000,
segment-3.ts
#EXTINF:6.000,
segment-4.ts
#EXTINF:6.000,
segment-5.ts
#EXTINF:6.000,
segment-6.ts
...

Assume we switch rendition based on bandwidth update.
We are selecting the next segment to load based on the buffered.end (assume current buffered is [0 - 12]).

Currently, we select segment-2.ts, but it is already buffered.

or assume we switch rendition based on a fast quality switch.
We are selecting the next segment to load based on the current time (current time is 12).

Currently, we select segment-2.ts but it is already played.

in both cases, we should select the next segment (segment-3.ts)

Specific Changes proposed

Select the next segment when we are at the exact segment.end boundary.

Requirements Checklist

• Feature implemented / Bug fixed
• If necessary, more likely in a feature request than a bug fix
  • Unit Tests updated or fixed
  • Docs/guides updated
  • Example created (starter template on JSBin)
• Reviewed by Two Core Contributors

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2878b27) 86.03% compared to head (e71202e) 86.03%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1467   +/-   ##
=======================================
  Coverage   86.03%   86.03%           
=======================================
  Files          42       42           
  Lines       10712    10715    +3     
  Branches     2462     2464    +2     
=======================================
+ Hits         9216     9219    +3     
  Misses       1496     1496           

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

[adrums86]

Great find.

[wseymour15]

Looks good to me, definitely fixes the issue. +1 after response to nit