[Critical] Persistent Global 429 Rate Limit on Paid Pro+ Account with Active Token Allocation

### Describe the bug

I am experiencing a critical and persistent global 429 Rate Limit error across all GitHub Copilot models and interfaces (CLI, Chat, and Free Fallback). This has persisted for over 3 hours despite a complete machine reboot and environment reset.

My account is a paid **Copilot Pro+** subscription. I have confirmed that I still have an active **token allocation quota**, and I also have sufficient **capital allocation/billing authorization** set up to pay for on-demand usage if the quota runs out.

The error states: "Sorry, you've hit a rate limit that restricts the number of Copilot model requests... (Request ID: ...)". This is not a usage-based limit, but an infrastructure-level block.

### Affected version

GitHub Copilot CLI 1.0.27 Experimental on

### Steps to reproduce the behavior

1. Authenticate with a valid Copilot Pro+ account.
2. Ensure you have active token allocation and a payment method set.
3. In the terminal, attempt any request, e.g., `copilot suggest "git commit message"` (or select ANY Premium model).
4. Observe the persistent immediate error: "Sorry, you've hit a rate limit...".
5. Wait for the specified duration (4 or 6 minutes) and retry.
6. Observe the error repeating immediately, or after a maximum of 2-3 requests, making the service unusable for over 3 hours.

### Expected behavior

As a Pro+ user with active allocation (both quota and payment method), I expect to be able to make requests to both standard and premium models, within the established concurrency limits, without experiencing immediate, global 429 blocks. I expect the system to properly utilize my allocation.

### Additional context

Here are the Request IDs of the failed requests:
1. `Request ID: EA0A:78AA1:35E2B4B:3A6FA59:69DFE000`
2. `Request ID: A8B0:E658E:41B81D8:47927BF:69E007BD`

Environment

OS: Ubuntu 24.04.4 LTS (Noble Numbat)
Kernel: Linux 6.17.0-19-generic
Architecture: x86_64
Desktop session: ubuntu:GNOME
Session type: X11
Shell: /bin/bash
Terminal environment: TERM=xterm-color

This seems to be a server-side provisioning or account state synchronization issue between the Billing API and the Copilot Gateway, as no local client resets (reboots, logging out) are resolving the block.