Fix Initialization, Actor Isolation, and `Package.resolved` Issues

[mhh-azam]

Description

This PR addresses the following issues:

1. Fix for Self Initialization Before Use:

   • Initialize displayName property before accessing self in the initializer.
   • This resolves errors related to accessing uninitialized properties.

2. Fix for Using Weak Self to Avoid Actor-Isolated Property Issue:

   • Capture self weakly in the MainActor.run block to prevent issues with actor isolation.
   • Avoids the error caused by passing actor-isolated properties as inout to async functions.

3. Fix for Resolving Corrupted Package.resolved File:

   • Deleted and regenerated the corrupted Package.resolved file to fix build errors.
   • Ensured that all dependencies are correctly resolved and consistent across environments.

Related Issues

• ISSUE_NUMBER

Checklist

• [x] I read and understood the contributing guide as well as the code of conduct
• [x] The issues this PR addresses are related to each other
• [x] My changes generate no new warnings
• [x] My code builds and runs on my machine
• [x] My changes are all related to the related issue above
• [x] I documented my code

Screenshots

[thecoolwinter]

I'm not too sure what you mean by the fix to the actor-isolated properties. This is currently compiling, so Swift doesn't seem to care about isolation here and the dispatch to the main actor is required to modify that property to make SwiftUI happy. Also correct me if I'm wrong but your patch doesn't fix actor isolation, it just weakly references self but still references everything else the same.