feat: Python native WSProxy

[kyujin-cho]

This PR introduces new variant of WSProxy, which in turn replaces our nodejs based local-proxy. After this PR is merged, developers can now launch local proxy by backend.ai wsproxy start-server command - just like we start other Backend.AI core components.
To start the WSProxy you need to set up a valid configuration file (wsproxy.toml). Check out configs/wsproxy for detailed configuration directives.

Checklist: (if applicable)

• Milestone metadata specifying the target backport version

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “flow:merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “flow:hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[kyujin-cho]

In the near future we can think of migrating contents of both wsproxy.api.utils and wsproxy.exceptions to our common repository so that it can be reused across other Backend.AI Core components.