fix: re-enable blob get notifications after migration is complete
See !939 (merged) for context. There we have temporarily bypassed the emission of blob get async notifications to avoid an unnecessary check against filesystem metadata that would always fail during the migration Phase 2. We should get back to this issue later and re-enable these notifications OR implement a proper solution that will play well with the phase 2 process and importer on self-managed.