fix(profile): stop sending maxResults to ListAvailableProfiles

[18005798765]

Summary

ListAvailableProfiles now rejects the maxResults field. Every call from listKiroProfilesInRegionContext returns:

HTTP 400 {"message":"Improperly formed request.","reason":"REQUEST_BODY_INVALID"}

The same request with an empty JSON body {} is accepted:

• Social (Google) account: 200 {"nextToken":null,"profiles":[]}
• Builder ID (idc) account: 403 AWS Builder ID is not supported for this operation. This is the error isBuilderIDProfileUnsupportedError already expects.

Because the 400 is neither the Builder ID 403 nor transient, ResolveProfileArn falls through to no available Kiro profile. ensureRestProfileArn then treats that as a hard error, so GetUsageLimits never runs. For Builder ID accounts this means usage and subscription info are never populated. getUsageLimits without a profileArn returns 200 with valid usage for those accounts.

Change

• Send {} on the first page and only nextToken when paginating. The unused pageSize constant is removed.
• The pagination test now asserts that the first page body does not contain maxResults.

Testing

• go test ./proxy/ passes.
• Deployed on a live instance. A Builder ID account that previously failed refresh with resolve profileArn: no available Kiro profile now refreshes and shows usage, limit, subscription title, and reset date. A social account still refreshes normally.

🤖 Generated with Claude Code