fix: show available liquidity for e-mode-only borrowable assets

[helpfulBro]

General Changes

• Fixes available liquidity showing $0 on the reserve overview for assets that are only borrowable in E-mode
• Builds on fix: show 0 for available liquidity if borrowing not enabled #3011, which correctly hides liquidity when borrowingEnabled is false — this extends that logic to also account for E-mode borrowability
• Adds assetIsBorrowableOnMarket() in getMaxAmountAvailableToBorrow.ts to check whether a reserve is borrowable in normal mode or any E-mode category (mirrors on-chain ValidationLogic behavior)
• Updates ReserveTopDetails.tsx to use the new helper for the "Available liquidity" display
• Adds unit tests in getMaxAmountAvailableToBorrow.spec.ts

Why this change?

Some reserves have borrowingEnabled: false in normal mode but remain borrowable when a user is in E-mode (via the category borrowableBitmap, exposed in the UI as eMode.borrowingEnabled). The reserve overview is market-level, so we show liquidity if the asset is borrowable through any path - not just normal mode.

How to verify

• Open a reserve where borrowingEnabled is false but the asset is borrowable in an E-mode → "Available liquidity" should show the actual USD value
• Open a reserve that is not borrowable in normal mode or any E-mode → "Available liquidity" should show $0
• Run yarn test getMaxAmountAvailableToBorrow

---

Reviewer Checklist

Please ensure you, as the reviewer(s), have gone through this checklist to ensure that the code changes are ready to ship safely and to help mitigate any downstream issues that may occur.

• End-to-end tests are passing without any errors
• Code changes do not significantly increase the application bundle size
• If there are new 3rd-party packages, they do not introduce potential security threats
• If there are new environment variables being added, they have been added to the .env.example file as well as the pertinant .github/actions/* files
• There are no CI changes, or they have been approved by the DevOps and Engineering team(s)

[vercel]

@helpfulBro is attempting to deploy a commit to the Aave Team on Vercel.

A member of the Team first needs to authorize it.