feat: upgrade api layer

[He1DAr]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

@stacks/blockchain-api-client no longer exports API call wrappers, we need to upgrade to latest stacks API JS client replace all API calls across Explorer.
https://github.com/hirosystems/stacks-blockchain-api/blob/HEAD/client/MIGRATION.md

Issue ticket number and link

closes #1896

Checklist:

• I have performed a self-review of my code.
• I have tested the change on desktop and mobile.
• I have added thorough tests where applicable.
• I've added analytics and error logging where applicable.

Screenshots (if appropriate):

N/A

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
explorer-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 27, 2024 3:20pm
hiro-explorer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 27, 2024 3:20pm

[codecov]

Codecov Report

Attention: Patch coverage is 15.77287% with 267 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/features/txsFilterAndSort/SortMenu.tsx	13.33%	26 Missing ⚠️
...ies/useAddressConfirmedTxsWithTransfersInfinite.ts	0.00%	15 Missing and 2 partials ⚠️
src/common/queries/useSearchQuery.ts	15.78%	15 Missing and 1 partial ⚠️
src/common/queries/useBlocksByBurnBlock.ts	13.33%	10 Missing and 3 partials ⚠️
...common/queries/useConfirmedTransactionsInfinite.ts	0.00%	13 Missing ⚠️
src/common/queries/useBlockTxsInfinite.ts	0.00%	10 Missing and 2 partials ⚠️
src/common/queries/useBurnBlock.ts	14.28%	9 Missing and 3 partials ⚠️
src/common/queries/useAccountBalance.ts	0.00%	11 Missing ⚠️
src/common/queries/useBlockByHash.ts	0.00%	9 Missing and 2 partials ⚠️
src/common/queries/useContractById.ts	0.00%	8 Missing and 3 partials ⚠️
... and 28 more

📢 Thoughts on this report? Let us know!

[He1DAr]

This function acts as a wrapper around the API client, it enforce type safety for the endpoint, parameters, and response, as well as providing centralized error handling. I had to use any when passing apiParams because the types provided by client library are not fully generic and rely on rigid definitions that cannot be dynamically inferred. Open to suggestions here.

[BLuEScioN]

I think this works. We'll do with the missing types for now, unless it hinders us in some signifcant way. Would be interesting to see if we could have done this with middleware, but I think that is a separate investigation. Thanks for making these changes!

[BLuEScioN]

One small thing about removing useBlockByHeight hook or w/e it was. Other than that LGTM