Bug/CLARK-CLIENT-1K/fix-undefined-collection-access

[sentry]

This PR addresses the TypeError: Cannot read properties of undefined (reading 'name') occurring in the learning object builder navbar (builder-navbar.component.html).

Root Cause: The collection object, which is populated asynchronously, was being accessed in the template without proper null guards. Specifically, the *ngIf condition only checked for learningObject?.collection (a string abbreviation) but not the collection object itself. This led to collection.name and collection.hasLogo being dereferenced when collection was still undefined during the asynchronous loading window. An inconsistency was noted as collection?.name was already used safely on line 42, but not on lines 45 and 48.

Fix:

1. Updated *ngIf guard: Modified the *ngIf condition on line 38 to include && collection. This ensures the block rendering collection.name and collection.hasLogo only executes once the collection object has been successfully resolved and is defined.
2. Added optional chaining: Applied optional chaining (?.) to collection.name (line 45) and collection.hasLogo (line 48) to prevent errors if collection were ever undefined for other reasons, aligning with the existing safe access pattern on line 42.

Fixes CLARK-CLIENT-1K

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}