Usefulness of `aspire update` is limited when we don't update other dependencies when CPM is in use.

When using `aspire update` a project can become unbuildable because we don't update all dependencies in `Directory.Packages.props` which may result in some package downgrade scenarios. Here is an example of a successful `aspire update` session with a test build of `aspire update` designed to overcome a compat issue 8.2.2 of Aspire. You can see that even those `aspire update` succeeded, it failed to succeed because of multiple pinned dependencies in CPM

[session.log](https://github.com/user-attachments/files/22529465/session.log)