fix(playground): listen to 127.0.0.1 instead of 0.0.0.0 for gRPC services

[BugenZhao]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

risedev d listens on 127.0.0.1 while playground (single-node) listens on 0.0.0.0. As a result, when there's a risedev d running in the background, starting risedev p can be confusing:

• meta node of p listens on 0.0.0.0, which does not conflict with risedev d and starts successfully
• then, compute node and frontend may connect to the meta node of d
• no error will occur as long as the wire protocol is compatible between the build of d and p, but the behavior can be quite weird

This PR changes the gRPC listen addresses of playground (single-node) to 127.0.0.1 as well to prevent this from happening. Please note that we continue to have the frontend pgwire service and the meta dashboard service listening on 0.0.0.0 to allow for remote connections.

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

[BugenZhao]

Already on L227