About temporary regressions in BlockSuite

[doodlewind]

Recently, we have been undergoing a major upgrade (#3165) to support new spec for defining third-party blocks. This will bring a well-defined API for the selection manager and a series of other standardized editor APIs, which will be documented in the future. Building on this new selection mechanism, we not only need to revamp the UI of widgets like drag handles and the format bar, but also migrate the existing selection data flow to address legacy issues with selection in edgeless and database (#1250). This will make these UI states to be collaboration-ready, allowing for multi-instance coexistence during collaboration.

To accelerate this process, we have proactively merged #3653 into the master branch. As a result, some test cases that have not yet passed are temporarily marked as FIXME. Due to our nightly release mechanism, versions that have not completely resolved regressions will also be released in the upcoming AFFiNE canary release. Consequently, we have received several issue reports (e.g., #3661 #3700 #3710 #3716 #3676 #3681 #3694 #3708). However, please rest assured that we are well aware of the scope of these problems and are prioritizing the resolution of these regressions (#3658). We plan to have them completely fixed before the next major AFFiNE release. Additionally, we have cherry-picked significant stability improvements and bug fixes onto the 0.7.1 branch to enhance the stability of the AFFiNE 0.7 version.