Fix: Add missing [weak self] in ServiceAlertViewController async closures

[diveshpatil9104]

Summary

ServiceAlertViewController captures self strongly in two async closures, preventing deallocation if the user navigates away before the page finishes rendering.

Problem

preparePage() dispatches work to a background queue and displayPage() dispatches back to the main queue — both capture self strongly. If the user opens a service alert and navigates back quickly, the view controller stays alive in memory until both closures complete.

Fix

Added [weak self] to both closures:

• preparePage() — background queue closure
• displayPage() — main queue closure with guard let self before accessing properties

Why this matters

This follows the convention already used throughout the codebase where async closures always use [weak self].

[aaronbrethorst]

Nice catch, Divesh — this is a clean and correct fix for a real memory management issue. The [weak self] pattern is exactly the right approach here, and it's consistent with how async closures are handled throughout the rest of the codebase.