v0.9.77

1. Fixed #1000

2. Supports #1004 (Less db locks)

3. Add QueryReason.FECHTER

4. Addressing the over-optimization issue with the save command, use smarter strategy.

   The save command supports using fetcher/viewType to control the format of the saved object. If the shape of the newly saved object is larger than what the fetcher/viewType requires, optimization is performed by directly trimming the current object instead of fetching it from the database.

   However, this optimization is problematic. Since Jimmer supports UpsertMask, certain properties of the user object may not always be saved to the database. Therefore, in such cases, the optimization should be abandoned, and the existing object should be considered untrustworthy, insisting on querying from the database.