feat(ui): improved canvas/queue error handling

[psychedelicious]

Summary

Improve error handling and logging for:

• Canvas layer rasterization, which occurs during transform, filter, select and crop operations
• Canvas layer compositing, which occurs during graph building
• Canvas generation mode calculations, which occurs during graph building

Minor additional changes:

• Remove duplicate log message when socket connects
• Simplify the handling of the enqueueRequested graph building RTK Q listener

Related Issues / Discussions

offline discussion

QA Instructions

These improvements should prevent canvas from getting stuck in a various processing states when an operation fails.

To test this, you could try this diff, which makes most uploads from within the app fail. This (hopefully) replicates a spotty/dropped network connection. There are other ways that canvas operations could fail, but this is the easiest way to induce this class of error.

diff --git a/invokeai/frontend/web/src/services/api/endpoints/images.ts b/invokeai/frontend/web/src/services/api/endpoints/images.ts
index 40b14201eb..8cbe368874 100644
--- a/invokeai/frontend/web/src/services/api/endpoints/images.ts
+++ b/invokeai/frontend/web/src/services/api/endpoints/images.ts
@@ -611,6 +611,7 @@ export const getImageMetadata = (
 
 export const uploadImage = (arg: UploadImageArg): Promise<ImageDTO> => {
   const { dispatch } = getStore();
+  throw new Error('Bork');
   const req = dispatch(imagesApi.endpoints.uploadImage.initiate(arg, { track: false }));
   return req.unwrap();
 };

Then try a transform & apply, filter, select object or crop to bbox.

• Before this PR: the canvas will get stuck with a grey-ed out Invoke button. The Invoke button tooltip will show a message like Canvas is busy (rasterizing) (maybe others if you were filtering or select-objecting).

• After this PR: you should see a toast saying which operation failed, then the canvas recovers gracefully, leaving you back in the state you were in before you started the failed operation.

  So for example, if it was applying a transform that failed, you should get a toast saying Failed to apply transform and the layer you were transforming should revert to the state it was in before you started the transform.

Merge Plan

Checklist

• The PR has a short but descriptive title, suitable for a changelog