fix(twitter/profile): recover counts + bio after X relocates them out of legacy (#2188)

[LeoLin990405]

Problem — #2188

opencli twitter profile <user> returns followers, following, tweets, likes all 0 and an empty bio, while name / screen_name / created_at / verified are correct.

Root cause: X (Twitter) relocated the count fields (followers_count, friends_count, statuses_count, favourites_count) and the bio (description) out of result.legacy into a new container — the same schema drift #1745 already handled for name/created_at by reading result.core. The adapter still read the counts and bio only from result.legacy, so they silently fell back to 0 / ''.

Fix

Rather than hard-code the (unknown, still-shifting) new path, mapTwitterProfileResult now resolves each affected field from its known homes first (legacy → core → top-level result), then falls back to a bounded breadth-first search that returns the shallowest match.

Shallowest-wins alone is not safe: when the field is absent from the user object entirely, an unrestricted BFS would descend into an embedded tweet and report its favourites_count as the user's likes, or its text as the bio. So the search refuses to cross into containers that describe a different entity (pinned_tweet, tweet, status, quoted_status, retweeted_status, entities, extended_entities, media, highlights). A wrong-but-confident number is worse than 0 / ''.

• Restores the counts and bio against the current payload.
• Stays robust if X relocates these fields yet again.
• Legacy-path responses (counts still under result.legacy) resolve identically — the existing test is unchanged.

Tests

mapTwitterProfileResult is a pure exported function. Added offline regression tests (12 total in the file):

• counts + bio recovered after relocation out of legacy (the [Bug]: twitter/profile returns 0 for followers/following/tweets/likes and empty bio (regression, opposite of #1745) #2188 case)
• canonical legacy values still win over a deeper decoy occurrence
• never falls back into an embedded tweet when the user field is absent → 0 / ''
• absent field everywhere → 0 / ''
• resolver rejects wrong-typed (numeric-string) and empty/whitespace values

npx vitest run clis/twitter/profile.test.js   # 12 passed
npm run typecheck                              # clean
npm run check:typed-error-lint                 # new=0
npm run check:silent-column-drop               # new=0

No change to the cli() registration, so cli-manifest.json is untouched.