Add X-RateLimit-Scope Header to Rate Limit Responses

If Ashby temporarily throttles an integration partner's combined traffic across organizations to protect service stability, the resulting 429 responses include the X-RateLimit-Scope: integration-partner header and a distinct error message. This lets partners tell these responses apart from per-API-key rate limits, which do not include the header.