refactor: improve network error and allow verbose output

[wylswz]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

• removed unreliable network error handling
• provided a global -v flag to allow verbose output
• moved http related properties from BaseError to HttpClientError

Screenshots

Before	After
...	...

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran make lint && make type-check (backend) and cd web && pnpm exec vp staged (frontend) to appease the lint gods

[lin-snow]

@wylswz

Thanks — redact message (ea3371e) looks correct, and rendering the body under verbose (1ef9b6b) gives -v a real effect now. A few leftovers:

1. Dead init.verbose still there. client.ts:137,141 still sets init.verbose = true on undici fetch, which ignores it. Now that verbose works via
   humanError()/isVerbose(), this line (and the verbose?: boolean type) is pure no-op — please remove it to avoid implying fetch-level verbosity.
2. raw_response is printed unredacted. errors/base.ts:134 pushes this.rawResponse directly — inconsistent with the redaction you just added. Suggest
   redactBearer(this.rawResponse).
3. Scope check. rawResponse is only set on 4xx/5xx (error-mapper.ts), not on 401 or transport errors, and toEnvelope() doesn't include it — so -v
   shows nothing for those paths or --format json. Fine as an MVP, just confirming it's intended.
4. (nit) trailing whitespace on errors/base.ts:127.

[wylswz]

@wylswz

Thanks — redact message (ea3371e) looks correct, and rendering the body under verbose (1ef9b6b) gives -v a real effect now. A few leftovers:

1. Dead init.verbose still there. client.ts:137,141 still sets init.verbose = true on undici fetch, which ignores it. Now that verbose works via
   humanError()/isVerbose(), this line (and the verbose?: boolean type) is pure no-op — please remove it to avoid implying fetch-level verbosity.
2. raw_response is printed unredacted. errors/base.ts:134 pushes this.rawResponse directly — inconsistent with the redaction you just added. Suggest
   redactBearer(this.rawResponse).
3. Scope check. rawResponse is only set on 4xx/5xx (error-mapper.ts), not on 401 or transport errors, and toEnvelope() doesn't include it — so -v
   shows nothing for those paths or --format json. Fine as an MVP, just confirming it's intended.
4. (nit) trailing whitespace on errors/base.ts:127.

1. It's a false positive.

[GareArc]

lgtm