refactor(web): convert ValidatedStatus enum to as-const in key-valida…

[guangyang1206]

…tor/declarations.ts

Closes #27998

The ValidatedStatus enum generates runtime code that inflates the bundle. Convert to an as-const object with a type alias instead:

Before:
export enum ValidatedStatus {
Success = 'success',
Error = 'error',
Exceed = 'exceed',
}

After:
export const ValidatedStatus = {
Success: 'success',
Error: 'error',
Exceed: 'exceed',
} as const

export type ValidatedStatus = typeof ValidatedStatus[keyof typeof ValidatedStatus]

All 65 call sites use ValidatedStatus.Success / .Error / .Exceed property access and type annotations — no changes needed there.

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Description

What problem does this PR solve?

Issue link: Closes #27998

What did this PR do?

Converts the ValidatedStatus TypeScript enum in web/app/components/header/account-setting/key-validator/declarations.ts to an as-const object with a type alias.

Before:

export enum ValidatedStatus {
  Success = 'success',
  Error = 'error',
  Exceed = 'exceed',
}

After:

export const ValidatedStatus = {
  Success: 'success',
  Error: 'error',
  Exceed: 'exceed',
} as const

export type ValidatedStatus = typeof ValidatedStatus[keyof typeof ValidatedStatus]

Why:
TypeScript enums generate runtime IIFE boilerplate that inflates the bundle. The as-const pattern produces zero runtime overhead while preserving the same dot-notation access (ValidatedStatus.Success) and TypeScript type safety.

Scope:
All 65 call sites use ValidatedStatus.Success / .Error / .Exceed property access or type annotations — they continue to work unchanged.

Checklist

• I have read the Contributing Guide
• This is a refactor/chore only
• No functional changes
• Related issue: refactor(web): In TypeScript, the use of enums should be avoided. #27998