refactor(thread): refactor hasCapability call with a better readable way

[Sma1lboy]

Update

LIST_CAPABILITY has been deprecated and will no longer be used.

Description

In the new version, we will no longer use hasCapability individually to check exposed APIs. Instead, we will obtain them during the communication establishment between two threads. Here we provide 1 protocol change and 2 inner thread methods.

Protocol Change

• EXPOSE_LIST
  Added a mechanism to exchange exposed APIs. When data is received, it will be automatically saved to cache.

Convention: Once two threads establish a connection, the exposed APIs will not be modified during this period.

Inner Thread Methods

• requestMethods: Only receive their APIs

Clarification: 'A' represents Outside (the IDE/client), while 'B' represents Inside (the server).

In our scenario, A is always created first, followed by B. This ensures B can successfully send messages to A. However, if A arrives too early, B might not receive the message signal. Furthermore, we only need A's Exposed APIs on the B side (server side). Currently, we only use requestMethods in createThreadFromInsideIframe.

By the way, we could also use exposed methods to check server's exposed APIs?

I have added numerous logs for now, which will be cleaned up after review.

Demo

Screenshot from log

Also the way we call in server side

      // proxy.has way
      if ('refresh' in server) {
        console.log('refresh in server')
      }
      // base on a server side trap method
      // no promise anymore, get answer instantally
      console.log('support v2?:', server?.supports['onApplyInEditorV2'])