[BUG] fail to use custom configurations for coordinator

[thweetkomputer]

Describe the bug
The coordinator's resource configuration is hard-coded. Users fail to use custom configurations.

To Reproduce

import graphscope

session = graphscope.session(
			k8s_coordinator_cpu=1)

Then use kubectl to describe the coordinator pod, the CPU is still the default value(0.5)

Expected behavior
The CPU should be 1

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• GraphScope version: [0.29.0]
• OS: Ubuntu
• Version 22.04
• Kubernetes Version [v1.30.2]

Additional context
Add any other context about the problem here.

[welcome]

Thanks for opening your first issue here! Be sure to follow the issue template! And a maintainer will get back to you shortly!
Please feel free to contact us on DingTalk, WeChat account(graphscope) or Slack. We are happy to answer your questions responsively.

[siyuan0322]

Yeah I thought this coordinator shouldn't cause much user attention, so for simplicity it's hardcoded. Any scenario that needs to customize:

[thweetkomputer]

Yeah I thought this coordinator shouldn't cause much user attention, so for simplicity it's hardcoded. Any scenario that needs to customize:

Hi Siyuan, I tried the kgs dataset on LDBC(https://ldbcouncil.org/benchmarks/graphalytics/). I used pandas to read the data and load the data through pandas, there is an OOM in the coordinator pod. I changed the memory of the coordinator to 2Gi and it's working now.

[github-actions]

/cc @yecol @sighingnow, this issus/pr has had no activity for a long time, please help to review the status and assign people to work on it.