feat(push): handle delete custom type with documents

[jomifepe]

Summary

• Detect Custom Types API 400 responses when deleting a type that still has documents (BadRequestError + stable checks on the response body).
• Resolve document counts via POST …/core/documents/search (Editor parity: customTypes + limit: 0), enforce the 200 bulk-delete limit, then call DELETE …/core/documents with customtype_ids before retrying type deletion.
• Errors include a deep link to the filtered builder working view: https://{repository}.{host}/builder/working?customTypes={id}.

---

Note

Medium Risk
Moderate risk: changes prismic push delete behavior and introduces new 400-error handling in the shared request helper, which could affect other callers’ error paths.

Overview
prismic push now wraps custom type deletions with additional handling: if the delete fails due to associated documents, it queries the document count and throws a clearer CommandError instructing the user to delete documents first, including deep links to the filtered working view and the custom type list.

To support this, the core client adds getDocumentTotalByCustomTypes() (via POST core/documents/search with limit: 0), Wroom adds URL builders for the working view and type lists, and the shared request() utility now throws a dedicated BadRequestError on HTTP 400 for more reliable detection.

^{Reviewed by Cursor Bugbot for commit 32ac787. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

There are 3 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 28c4453. Configure here.}