Current Time and Duration not correct after live ended on v4.7.3

[KunXi-Fox]

Environment

• The MPD passes the DASH-IF Conformance Tool on https://conformance.dashif.org/
• The stream has correct Access-Control-Allow-Origin headers (CORS)
• There are no network errors such as 404s in the browser console when trying to play the stream
• The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ
• The issue occurs in the latest reference client on http://reference.dashif.org/dash.js/ and not just on my page

• Dash.js version: 4.7.3
• Browser name/version: Chrome v123.0.6312.122
• OS name/version: Mac

Steps to reproduce

watch a live event and wait for it's end

Observed behavior

the current time is much larger than duration

Console output

• currentTime comes from dashInstance.time()
• duration comes from dashInstance.duration()
• _duration comes from dashInstance.duration() for last dynamic manifest

More information

The issue introduced by this PR

• Fix/control bar #4314

As far as we know

1. currently we're not process the up coming flow when manifest changes from dynamic to static.
2. time and duration calculations totally based on isDynamic
3. based on 1, it's ok to still calculate time and duration with dynamic

After above pr merged

1. when we call the time method, isDynamic will return false to us, so we'll not reduce the dvr.start, which leads to a wrong current time.

// we'll not run into this code segment
t = (metric === null || t === 0) ? 0 : Math.max(0, (t - metric.range.start));
return t;

2. when we call the duration method, we'll return videoElement.duration which is still Infinity.

let d = getVideoElement().duration;

if (playbackController.getIsDynamic()) { // we'll not run into this code segment anymore.
    const type = streamController && streamController.hasVideoTrack() ? Constants.VIDEO : Constants.AUDIO;
    let metric = dashMetrics.getCurrentDVRInfo(type);
    d = metric ? (metric.range.end - metric.range.start) : 0;
}
return d;