Devel -> Main - CLAP fix and improvement

[NeptuneHub]

This contain multkiple clap fix and improvement.

In general, the fix is to avoid returning the raw exception string to the client and instead return a generic error message, while logging the detailed exception on the server. This aligns with the pattern shown in the background “GOOD” example.

Concretely, in warmup_model_api (lines 132–140), we should keep logging e but change the JSON response so that the "error" field contains a generic message like "Model warmup failed" instead of str(e). This preserves existing behavior in terms of HTTP status code (500) and the "loaded": False flag, but prevents any sensitive error details from leaking.

Only this region in app_clap_search.py needs modification:

• Around line 135: keep logger.error(f"Model warmup failed: {e}") as-is.
• Around lines 137–139: replace 'error': str(e) with a generic, non-sensitive message. No new imports or helper methods are required.

In general, the fix is to avoid returning raw exception messages or stack traces to clients. Instead, log the detailed exception on the server (with stack trace) and respond with a stable, generic error message and, optionally, a non-sensitive error code that the client can use.

For this specific code, the minimal change is inside warmup_model_api in app_mulan_search.py:

• Keep logging the failure, but enrich the logging with the full stack trace so developers still have diagnostics (e.g., logger.exception(...) or logger.error(..., exc_info=True)).
• Replace the JSON 'error': str(e) field with a generic message such as 'error': 'MuLan model warmup failed', which does not depend on the exception content.
• Preserve the existing HTTP status code (500) and the 'loaded': False flag so external behavior besides the message content remains the same.

Concretely:

• Modify the except Exception as e: block around lines 135–140:
  • Change the logging call to include traceback information.
  • Change the JSON payload to use a constant generic message instead of str(e).

No new imports are required if we use logger.exception, since logging is already imported; otherwise, we could pass exc_info=True to logger.error without new imports.