fix emode tests

[mgrabina]

E-Mode just limits borrow-side. So when asking for market reserves, canBeCollateral (allowing users to set new supplies as collateral) is not affected by active e-mode and specific reserve's e-mode's config is only used in borrow-side for HF (and collateral amount calculation).

Example:
A user supplies ETH and activates e-mode ETH-correlated. the user can now only borrow ETH-correlated assets, and his HF is calculated based on collateral from reserves in ETH-Correlated, but he still can supply USDC and set it as collateral.
Not useful in terms of improving custom HF, but he can still earn rewards from it and leave it ready in case he turns e-mode off.

Now both related tests are passing

Closes AAVE-857, AAVE-858

[cesarenaldi]

But the flag you are changing the assertion on is about if the user can use the given supply as collateral, not if they can supply it.

[mgrabina]

@cesarenaldi yeah, by supply i meant supply + using as collateral

[cesarenaldi]

what's the implication of activating a collateral on a supply reserve that is not part of the emode?

[linear]

AAVE-868 [BUG] when fetching borrowAPY or supplyAPY history for windows more than a day is not working

working request:

const result = await supplyAPYHistory(client, {
  market: ETHEREUM_MARKET_ADDRESS,
  chainId: ETHEREUM_FORK_ID,
  underlyingToken: WETH_ADDRESS,
  window: TimeWindow.LastDay,
});

when changing the timeWindow form "lastDay" to "lastMonth" I am not getting any result.

AAVE-858 [BUG] E-Mode not reflected in MarketUserReserveSupplyPosition

The specific e-mode category reserves settings (e.g., canBeCollateral, canBeBorrowed) are not reflected on the MarketUserReserveSupplyPosition for any user supply position.

• supply position for tokens not listed in the e-mode category reserves should be considered as not be usable as collateral
• supply position for tokens included in the e-mode category reserves should follow the specified e-mode category settings

## First Setup

nvm use
pnpm install
pnpm build

## Run Test Scenario
pnpm run test:858

[linear]

AAVE-857 [BUG] E-Mode not reflected in Reserve.userState

The specific e-mode category reserves settings (e.g., canBeCollateral, canBeBorrowed) are not reflected on the Reserve.userState for a user that enabled the specific e-mode category.

## First Setup

nvm use
pnpm install
pnpm build

## Run Test Scenario
pnpm run test:857

[cesarenaldi]

Let's remove this line altogether then, this is the same as not checking it.