Pagination queries for balances endpoint

[rafal-ch]

Closes #2023

TODO:

• Add integration test due to custom logic related to base asset id
• Make it work properly with base asset id

Description

This PR enables the paginated queries for balances, but only if the balance indexation is enabled. Otherwise, the attempt to send paginated query will result with Can not use pagination when balances indexation is not available error.

Checklist

• New behavior is reflected in tests

Before requesting review

• I have reviewed the code myself

[xgreenx]

Suggested change

	#[graphql(complexity = "query_costs().balance_query")]
	#[graphql(complexity = "query_costs().balance_query + query_costs().storage_iterator \
	+ (query_costs().storage_read + first.unwrap_or_default() as usize) * child_complexity \
	+ (query_costs().storage_read + last.unwrap_or_default() as usize) * child_complexity\")]

We need to limit the number of requested balances=)

[xgreenx]

It also makes this change breaking

[rafal-ch]

Updated in fd2b019

[xgreenx]

Yeah, it is a tricky function because of how we handle balances.

Hmm, do you remember why we decided to skip balances during iteration and add them at the begin?

I remember: if you don't have coins but have messages, they will not appear during the iteration.

The problem with the current solution is when start == base_asset_id. The current code will return an incorrect iterator.

Either we need to handle it differently, or come up with another solution. It would be nice if we could insert base asset balance into the mid of the iterator. Maybe we could change the indexation and make it always add empy indexation for the base asset(like entry in the balances table with 0 amount just for balances)?

Then during iteration we call always fetch its value by using self.base_asset_balance?

[rafal-ch]

These two commits should solve the problem

[rafal-ch]

Converting to draft, some rework is needed here.