fix(vscode): throw on missing accessToken instead of returning '******'

[Copilot]

getAuthorizationToken was silently returning '******' when no access token existed, causing callers (e.g. the periodic token refresh) to send invalid `Authorization: ****** headers to ARM.

Changes

• getAuthorizationToken.ts: Guard against missing accessToken — throws 'No access token available. Please sign in to Azure.' instead of returning an invalid ****** Removed redundant ?. on the return path since the guard guarantees truthiness.

  // Before
  return `******; // returns "******" when no session
  
  // After
  if (!authData?.accessToken) {
    throw new Error(localize('noAccessToken', 'No access token available. Please sign in to Azure.'));
  }
  return `******;

• __test__/getAuthorizationToken.test.ts (new): Test file from PR fix(vscode): Fix Workflow save, token persistence #9406 with the unsafe assertion fixed — the no-token case now asserts rejects.toThrow('No access token available') instead of toBe('******').

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

getAuthorizationToken returned '******' when no access token was available, propagating an invalid auth header to downstream ARM requests. This is a targeted fix to throw instead, surfacing the real problem early.

Impact of Change

• Users: Auth failures now surface as a clear error rather than a silent invalid-token request.
• Developers: Callers of getAuthorizationToken must now handle the thrown error when no session exists.
• System: No architectural changes.

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:

Contributors

Screenshots/Videos