Handle errors when renaming worker configurations

https://redmine.teklia.com/issues/9133

Errors with duplicate configuration names are handled when creating configurations, but not when renaming them through the EditableName component.

When the updateConfiguration store action handles API errors, it should look for a name property first and pass that to the errorParser, and fall back to the error itself when there is no name. This will cause the notification to show A worker configuration with this name already exists for this worker. instead of Request failed with status code 400.