Architecture optimization for AFFiNE cloud

[zuoxiaodong0815]

Our team has identified several areas that need to be optimized to improve code stability. We plan to implement the following changes:

Improve code readability

Beta Give feedback

1. optimize blob's code #377
   +0
   

• Improve error handling AFFiNE#1772
• Server-side transaction mechanism: The transaction mechanism will help us avoid data inconsistency and ensure that all requests are processed reliably and consistently.
• Generate a unique ID for every request AFFiNE#1585
• Ensure the idempotency of API requests: We will ensure that API requests are idempotent, meaning that multiple requests do not have unexpected effects. This will help us avoid data inconsistency and ensure that our system remains stable.
• Improve system security： Enhance user permissions, and check for issues such as unauthorized access.
• check permissions of blob API

These optimizations will help us create a more stable and efficient system, improving code stability and enhancing the user experience.

[zuoxiaodong0815]

Found an issue, the token nonce should not be constant, it's very dangerous to do so.

[zuoxiaodong0815]

The issue of API idempotence is mainly related to the following three APIs:
/api/workspace POST
/api/workspace/:id DELETE
/workspace/:id/blob. PUT