Improve frontend stability

[zuozhiw]

This PR improves the stability of the frontend by making two changes:

1. After adding the lock related logic, we have an increasing number of error ExpressionChangedAfterItHasBeenCheckedError. When this error occurs, some components on the frontend might become freezing or unresponsive.
   

This is due to not running angular change detection after the lock status is changed. We have manually added change detection check whenever lock status is changed. This is also one of Angular's recommended ways to fix it.

2. After adding the async rendering functionaility, we found another JointJS related bug. This error is more likely to happen when switching workflows in version control. When this error happens, JointJS cannot render the operator links.
   

This is due to an internal bug in JointJS, see clientIO/joint#1320 . We have adopted a recommended workaround to fix this issue. Thanks @MysteriousChallenger for identifying and solving this issue.

[MysteriousChallenger]

This fixes the version switcher bug where links disappear

[Yicong-Huang]

I have met this ExpressionChangedAfterItHasBeenCheckedError in another branch (maybe seen after upgrade of jointjs, I could be wrong). I wonder what is the best practice to avoid this error? also what kind of component would need to consider run change detection manually?

[Yicong-Huang]

left a question regarding the detechChange solution.