[HUM-164]: feat: add new http api client

[mpblocky]

Issue tracking

HUM-164

Context behind the change

• added new http api clients: authorized, unauthorized, auth service
• migrated all endpoints to use it
• removed dead code related to fetcher

How has this been tested?

• tested every endpoint to ensure it works as before

Release plan

normal

Potential risks; What to monitor; Rollback plan

Monitor incorrect requests in case there was something that was omitted during testing

[vercel]

@mpblocky is attempting to deploy a commit to the HUMAN Protocol Team on Vercel.

A member of the Team first needs to authorize it.

[mpblocky]

@dnechay This one is ready. I know it's huge but I tried to commit every piece separately for easier review. LMK if You need something!

[mpblocky]

@dnechay small fixes for my jobs needed, will let You know

[mpblocky]

@dnechay ready

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
human-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 23, 2025 8:43am

[dnechay]

HTTP clients & auth handling lgtm as for now
Some comments below

1. You don't have to create an instance of HttpApiClient or AuthorizedHttpApiClient in every specific service, they all have the same base api url, so you can create these instances once and simply use them later w/o wrapping in any classes, e.g.

import { humanAppApiClient } from '@/api';
...
const result = await humanAppApiClient.post<SignatureData>(
  apiPaths.web3.prepareSignature,
  {
    body: { ...data },
    successSchema: prepareSignatureSuccessSchema,
  }
);

return result;

2. Deployment fails due to build errors, please check them

[mpblocky]

@dnechay everything addressed

[dnechay]

Looks better!

Two comments from previous review are still actual: №1, №2 and some minor items to cleanup

1. "Reset Password" functionality is not working due to absence of h_captcha_token in payload
2. After registering address for worker, tokens are refreshed, but Register button is still there. Seems like some extra step need for updating user state when doing authService.refreshAccessToken

[mpblocky]

@dnechay fixed!

[dnechay]

LGTM

1. Please resolve merge conflicts
2. On example of OperatorProfileService.enableOperator, could you please make this and similar methods where we expect "fire & forget" to look like

async enableOperator(signature: string) {
  try {
    await authorizedHumanAppApiClient.post(
      apiPaths.enableOperator,
      {
        body: { signature },
      }
    );
  } catch (error) {
    ...
  }

so it's clear that it's not expected to handle any return value from it