feat: update common version and remove jersey code

[zhenyuT]

Purpose of the PR

之前提过一个draft PR(已关闭)：

• feat(client): replace jersey with okhttp in hugegraph-client (Draft PR) #508

直接在client中将jersey相关代码用okhttp替换掉。

对应的issue见：

• [Feature] Replace jersey in hugegraph-client/common to avoid SpringBoot/Jarkata conflicts #505

后面将对应的实现在common中进行实现，并提交了PR(已合入主分支)：

• feat(common): replace jersey dependencies with OkHttp (Breaking Change) incubator-hugegraph-commons#133

所以现在需要对toochain的代码进行整改，升级common版本，并进行代码适配，移除jersey相关的代码

Main Changes

Verifying these changes

• Trivial rework / code cleanup without any test coverage. (No Need)
• Already covered by existing tests, such as (please modify tests here).
• Need tests and can be verified as follows:
  • xxx

Does this PR potentially affect the following parts?

• Nope
• Dependencies (add/update license info)
• Modify configurations
• The public API
• Other affects (typed here)

Documentation Status

• Doc - TODO
• Doc - Done
• Doc - No Need

[javeme]

Great improvement, hopefully we can get rid of jersey's issues from now on.

[javeme]

@imbajin can we share the same COMMIT_ID with client-ci.yml (just use an global env var)

[imbajin]

@imbajin can we share the same COMMIT_ID with client-ci.yml (just use an global env var)

I do want it too but not found the way to achieve it, however I get a better way to avoid hard code commit ID in ci

we could use "latestCommitID - X" (X >= 15 maybe) to get the stable code in server & no need update the ID by ourselves if not necessary (will submit a PR after this adaptor) #542

[javeme]

It is a method to use latestCommitID - X, but we can't control it freely. If we want to adapt to the latest code, we still need to change the X.
we may try reusable-workflow: https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow

[imbajin]

It is a method to use latestCommitID - X, but we can't control it freely. If we want to adapt to the latest code, we still need to change the X. we may try reusable-workflow: docs.github.com/en/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow

Get it, but we can't set secrets/variables in settings, we lack the permission to set it 😢 (This is also the reason why in the early code, we could only write fixed commitID in multiple CI files)

BTW, we could create/submit a common action and publish it to github action repo & let other actions to extend it if github supports

[imbajin]

LGTM