Migrate RPC to ConnectRPC

[chacha912]

What this PR does / why we need it?

Migrate RPC to ConnectRPC. For more information about this migration, follow:

• https://github.com/yorkie-team/yorkie/pull/703
• https://github.com/yorkie-team/yorkie-js-sdk/pull/698

Any background context you want to provide?

• Add error_details.proto

  // NOTE(chacha912): This code is based on the protobuf definitions from the file located at:
  // https://buf.build/googleapis/googleapis/file/main:google/rpc/error_details.proto.
  // The protobuf definitions are compiled into an SDK, which can be installed via npm.
  // (SDK Source: https://buf.build/googleapis/googleapis/sdks/main)
  //
  // However, during testing, we encountered an error due to the use of ESM import/export syntax.
  // To address this issue, we use the 'js_import_style=legacy_commonjs' option and manually build
  // the protobuf, rather than using the SDK directly.
  // (For more details, refer to: https://github.com/bufbuild/protobuf-es/issues/587)

• JSDOM Environment Patch for TextEncoder and TextDecoder

  // NOTE(chacha912): This patches the global objects TextEncoder, TextDecoder
  // which are missing in the JSDOM environment.
  // See https://github.com/jsdom/jsdom/issues/2524 for more details.

• Introduction of Custom Thunk
  • To handle common processing for asynchronous actions, a custom thunk has been introduced. For more information, please refer to the documentation in the rpc-error-handling.md.

What are the relevant tickets?

Fixes #

Checklist

• [x] Added relevant tests or not required
• [x] Didn't break anything

[hackerwins]

Thanks for your contribution.