[S4] Add request timeout and standardise error parsing in the API client

[Akshola00]

Description

The axios instance in lib/api-client.ts has no timeout configured. A hanging request will block the UI indefinitely with no feedback to the user. Additionally, API errors come back in different shapes ({ message }, { error }, plain strings) and each caller handles them differently.

Deliverables

• Add timeout: 10_000 (10 seconds) to the axios instance configuration in lib/api-client.ts
• Add a parseApiError(err: unknown): string helper in the same file (or lib/errors.ts) that extracts a human-readable message from any axios error shape
• The helper should handle:
  • err.response.data.message (NestJS default)
  • err.response.data.error
  • err.message (network/timeout errors)
  • Fallback: 'Something went wrong. Please try again.'
• All existing callers that catch API errors should use parseApiError
• npm run build passes

Notes

No new dependencies — this uses only what axios already provides.

[victor62-art]

@victor62-art has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

pls assign me this issues

ℹ️ Repo Maintainers: To accept this application, review their application or assign @victor62-art to this issue.

[RemmyAcee]

@RemmyAcee has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @RemmyAcee to this issue.

[Luchistack]

@Luchistack has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Luchistack to this issue.