Improve GQL mutation's exception handling logic

[jopemachine]

Motivation  

• To enable more detailed error handling of GQL mutation failures on the frontend, the current method of relying on ok and msg needs to be improved.
• Not only must the return type of all GQL mutations be modified, but the corresponding SDK, WebUI, and Control Panel logic that utilizes them also need to be updated.

Objective

• Improve GQL mutation's common return type
• Improve GQL Mutation exception handling Logic on the Client Side
• The issue itself is relatively easy in complexity, but since this change introduces a big breaking change, care must be taken to avoid conflicts with the client side.

�Expected Sub Issue

• Remove ok, msg from the current codebase’s GQL mutations.
• Raise GraphQLError instead of using ok, msg.