fix(alicloud_cs): remove incompatible Connection header

[Copilot]

alicloud_cs.ts was sending HTTP/1.x hop-by-hop headers (not RFC8441-compatible) on request paths that may use HTTP/2.
This change makes header construction protocol-aware: only non-HTTPS paths retain Connection: keep-alive; HTTPS paths omit it.

• Problem scope

  • AliCloud QR-login/auth request flow used a shared header builder with unconditional Connection.
  • RFC8441 compatibility requires avoiding hop-by-hop headers on H2-capable paths.

• What changed

  • Introduced URL protocol check in AlipanQRLogin (isHttpsUrl).
  • Refactored header builder to getHeaders(targetUrl) so header decisions are made per request target.
  • Updated all relevant call sites (getOAuthUrl, getLoginPage, generateQRCode, queryQRStatus) to pass their target URL into the header builder.
  • Kept behavior unchanged for non-HTTPS targets by conditionally adding Connection: keep-alive only there.

• Resulting behavior

  • HTTPS (H2-capable) requests: no Connection header.
  • Non-HTTPS requests: Connection: keep-alive preserved.

private getHeaders(targetUrl: string): Record<string, string> {
  const headers: Record<string, string> = {
    'User-Agent': '...',
    'Accept': 'application/json, text/plain, */*',
    'Accept-Language': 'zh-CN,zh;q=0.9,en;q=0.8',
    'Accept-Encoding': 'gzip, deflate, br',
    'Sec-Fetch-Dest': 'empty',
    'Sec-Fetch-Mode': 'cors',
    'Sec-Fetch-Site': 'same-site',
    'Referer': 'https://passport.alipan.com/',
    'Origin': 'https://passport.alipan.com'
  };

  if (!this.isHttpsUrl(targetUrl)) {
    headers.Connection = 'keep-alive';
  }
  return headers;
}

[jyxjjj]

等我白天改，Copilot真不如GPT，这样改动还不如直接删下请求头，看来是我提示词说太多了

I have reverted AI's edition & force pushed