indexer-agent: maxAllocationEpochs not being considered when identifiyng expired allocations

[oselezi]

Multiple indexers have reported that the Indexer Agent will close and renew allocations one epoch after creation.

This means that the maxAllocationEpochs value provided by the Staking contract is not being considered when identifying expired allocations during the reconciliation loop.

Requirements

• The Agent must only close allocations when they are duly expired.

• For a better indexer experience, add logs that inform how the allocation expiration epoch was calculated: either by an indexing rule, the maxAllocationEpoch value obtained from the Staking contract, or the minimum default of one epoch.