setOtherCursor call behaviour different in monaco and ace

[lakbychance]

Describe the bug
setOtherCursor method of ace-adapter.ts is called on both the current user and remote user when current user is typing on same line as remote user. If they are on different line, only when remote user types setOtherCursor gets called on current user. While in case of monaco-adapter.ts, setOtherCursor method is only called when the remote user is typing.

To Reproduce
You can set a console.log(...) inside setOtherCursor method of ace-adapter.ts and monaco-adapter.ts to verify the behavior with two different client sessions.

Expected behavior
Have little knowhow here. But the diverging behavior between two implementations is the main concern.

Desktop :
OS: macOS
Browser Chrome

Additional context
This behavior should be addressed on priority because cursor/selection and tooltip implementation depends on setOtherCursor call done right.