Fix #4042: Implement success criteria metrics for lesson checkpointing

[theMr17]

Explanation

Fixes #4042

This PR implements the success criteria metrics required for lesson checkpointing as described here. A high level overview of the implementation is documented on the issue thread here.

Changes to FakeAnalyticsEventLogger

• fun getOldestEvents(count: Int): List<EventLog> is necessary to retrieve a list of a pre-defined count of oldest events from all the logged events.
• fun getLoggedEvent(predicate: (EventLog) -> Boolean): EventLog? serves to acquire a reference to a logged event when the context of the event is known, but the event index is uncertain or potentially surrounded by other events. Thus, extracting the event via index might be difficult.

Essential Checklist

• The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• Any changes to scripts/assets files have their rationale included in the PR explanation.
• The PR follows the style guide.
• The PR does not contain any unnecessary code changes from Android Studio (reference).
• The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
• The PR is assigned to the appropriate reviewers (reference).

For UI-specific PRs only

If your PR includes UI-related changes, then:

• Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
• For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
• Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
• For PRs introducing new UI elements or color changes, both light and dark mode screenshots must be included
• Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

[oppiabot]

Hi @theMr17, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[theMr17]

@adhiamboperes PTAL.

[adhiamboperes]

Thanks @theMr17!

I have left a comment on the failing eventlog test, please let me know if I need to clarify it further.

[theMr17]

@adhiamboperes PTAL. I have reintroduced the getLoggedEvent(predicate: (EventLog) -> Boolean): EventLog? function. I have also included tests for the new functions added in FakeAnalyticsEventLogger.

[adhiamboperes]

Thanks @theMr17! This LGTM!

[oppiabot]

Hi @theMr17, this PR is ready to be merged. Please address any remaining comments prior to merging, and feel free to ask someone to merge your PR once the CI checks pass and you're happy with it. Thanks!

[oppiabot]

Hi @theMr17, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!