Only pass in view models for screens for writable cases. If its read-only, just pass in the object.

Pre-Flight checklist

• Did you check to see if this issue already exists?
• This is a single feature request. (Do not put multiple feature requests in one issue)
• This is not a question or discussion. (Use https://lemmy.ml/c/jerboa for that)

Describe The Feature Request Below

On many of the screens, we pass in large view models, which let you refetch and update data. For example, we pass in the siteViewModel, appSettingsViewModel, and accountViewModel into screens where it shouldn't need to write or update those objects, only read them.

This isn't ideal because:

• It exposes the objects within as writeable, where many shouldn't be.
• We then have to observeAsState, whereas in most cases we should only need to have the GetSiteResponse or AppSettings

We should go through every screen in MainActivity.kt, and make sure its only passing the minimum of what it needs.

Start in MainActivity.kt and review each screen's parameters, especially uses of siteViewModel, appSettingsViewModel, and accountViewModel. Identify screens that only read data and determine the smallest read-only values they need instead of writable view models. Done means every screen receives only the minimum required data while writable cases retain the needed update access.