Integrate Presto services into CLP Package Docker Compose project

[coderabbitai]

Context

As documented in PR #1310, the current Presto integration requires users to set database.host to a non-localhost hostname/IP because the Presto containers run on a Docker network while CLP's database runs on the host network. This mitigation is practical but inconvenient for users operating in diverse network environments.

Long-term Solution

Integrate the Presto services into the CLP Package Docker Compose project introduced in #1178. The tools/deployment/presto-clp directory is only 132 KB in size, so this integration would not significantly increase the package size while substantially improving user convenience.

Benefits

• Eliminates the need for non-localhost hostname configuration
• Provides a unified deployment experience
• Simplifies network connectivity between CLP and Presto services

References

• PR docs(presto-clp): Add instructions for connecting CLP's UI to Presto; Simplify some set up instructions. #1310: docs(presto-clp): Add instructions for connecting CLP's UI to Presto; Simplify some set up instructions. #1310 (comment)
• Original Presto Docker Compose addition: feat(presto-clp): Add Docker compose setup for Presto cluster that can connect to clp-json. #1132
• CLP Package Docker Compose project: feat(deployment)!: Migrate package orchestration to Docker Compose (resolves #1177); Temporarily remove support for multi-node deployments. #1178
• Requested by: @junhaoliao