feat(medium-pass-1): register MediumPass callbacks in ActionCreator

[lisli1]

Details

This PR ensures that the MediumPass/QuickAssess equivalents of Assessment callbacks are registered in ActionCreator

Motivation

Part of feature work

Context

Pull request checklist

• [n/a] Addresses an existing issue: #0000
• Ran yarn null:autoadd
• Ran yarn fastpass
• Added/updated relevant unit test(s) (and ran yarn test)
• Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
• PR title AND final merge commit title both start with a semantic tag (fix:, chore:, feat(feature-name):, refactor:). See CONTRIBUTING.md.
• [n/a] (UI changes only) Added screenshots/GIFs to description above
• [n/a] (UI changes only) Verified usability with NVDA/JAWS

[madalynrose]

This looks great! One question: why don't we need separate callbacks for onStartOverTest and onCancelStartOver when we do have separate callbacks for onStartOverAllAssessments and onCancelStartOverAllAssessments?

[waabid]

LGTM!

[waabid]

This looks great! One question: why don't we need separate callbacks for onStartOverTest and onCancelStartOver when we do have separate callbacks for onStartOverAllAssessments and onCancelStartOverAllAssessments?

I believe it's due to telemetry event names being specific for Assessment or not. If they are not specific, we can use the same functions.

The visualization type will be different though, so we'll still be able to differentiate FWIW.