Fix: RequestHelper silently swallows non-2xx responses, causing false success on Upload & Publish

[Copilot]

RequestHelper.requestData/postData/patchData returned undefined for any non-2xx, non-401 response. Callers like uploadWebResourceInternal never entered their catch block and unconditionally showed the success toast — even when the PATCH or PublishXml was rejected server-side (lock conflicts, permission errors, 503s, etc.).

Changes

• requestHelper.ts: Replace return undefined in the non-Unauthorized error branch of all three HTTP methods with a call to a new raiseResponseError helper that throws instead.
• raiseResponseError (new private method): Parses the Dataverse JSON error body (error.message / error.code) and throws with the server's human-readable message; falls back to Request failed with status {N} if the body is unparseable.
• Removed the unused redirectTimeout stub.

// Before — failure silently discarded
} else {
    return undefined;
}

// After — server error surfaced to caller
} else {
    await this.raiseResponseError(response);
}

The existing catch in uploadWebResourceInternal already shows ErrorMessages.wrUploadError and logs the error — no changes needed there. Dataverse lock-conflict messages (e.g. "A solution import is in progress") will now appear verbatim in the error toast.

• Fixes [Bug]: Upload & Publish reports success when the update or publish actually fails #342