feat: add option to force start rag-api-server

[DarumaDocker]

No description provided.

[juntao]

Hello, I am a code review agent on flows.network. Here are my reviews of changed source code files in this PR.

---

gaianet

Potential issues

1. Issue: The grep command used in check_config_options() and other places is case-sensitive and may miss fields with different casing.

   • Explanation: Using grep -q '"address":' will only match "address": exactly, but it won’t match "Address":, "ADDRESS":, etc.

2. Issue: The ulimit -n 10000 command is applied to both Darwin and Linux, which might not be appropriate for all environments.

   • Explanation: Setting the file descriptor limit without checking current limits or providing an option to customize it can lead to unexpected behavior on systems with different requirements.

3. Issue: The nohup commands are used extensively but do not redirect both stdout and stderr properly, which can lead to incomplete logging.

   • Explanation: While most nohup commands use > $log_dir/some.log 2>&1, there are a few instances like nohup supervise $gaianet_base_dir > $log_dir/start-vector.log 2>&1 & that might not capture all error logs if supervise writes to stderr in unexpected ways.

Summary of changes

• • Added force_rag parameter to the start() function to allow forcing the start of rag-api-server.
• Modified condition to start Qdrant instance to include the case when force_rag is true.
• Introduced a new command-line option --force-rag to enable forced starting of rag-api-server.

[apepkuss]

How about use --force-rag instead of --rag? Thanks!