feat(actions): add PRESENT_POI and RESIZE action types for Horizon allocations

[MoonBoi9001]

Motivation

Horizon allocations are long-lived and benefit from operations that don't require closing and reopening. This PR adds two new action types that operate on existing allocations: one for collecting rewards by posting a POI, and one for adjusting stake.

Summary

Add two new action types for Horizon allocations:

PRESENT_POI - Posts a POI on-chain to collect indexing rewards without closing the allocation. Enables periodic reward collection while keeping allocations active.

RESIZE - Changes the staked amount on an existing allocation without closing it. More efficient than reallocate for stake adjustments on long-lived allocations since it avoids POI submission and reward collection overhead.

Changes

PRESENT_POI

• ActionType.PRESENT_POI enum value
• GraphQL presentPOI mutation and PresentPOIResult type
• Database model validation and migration
• AllocationManager methods (preparePresentPOI, confirmPresentPOI, etc.)
• CLI: graph indexer actions queue present-poi <deployment> <allocationID> [poi] [force] [blockNumber] [publicPOI] -n <network>

RESIZE

• ActionType.RESIZE enum value
• GraphQL resizeAllocation mutation and ResizeAllocationResult type
• Database model validation and migration
• AllocationManager methods (prepareResize, confirmResize, etc.)
• CLI: graph indexer actions queue resize <deployment> <allocationID> <amount> -n <network>
• IE087 error code for resize failures

Shared

• Unit tests for action validation
• Stake usage summary handling for both action types

Contract interfaces

// PRESENT_POI
function presentPOI(allocationId, poi, poiMetadata) external

// RESIZE
function resizeAllocation(indexer, allocationId, tokens) external

---

Generated with Claude Code

[tmigone]

Have not reviewed in detail yet, but first comment is I think we should rename from COLLECT to something else. Collect refers generically to any payment type, could be indexing rewards, query fees or something else. Historically also "collect" has been associated with query fees, so this would be confusing I think.

What do you think about switching to something thats more related to what happens to the allocation (poi is posted on chain) and not the side effect (which is rewards are collected). So could be "present/post poi": graph indexer actions queue present-poi ... or something along that vein.

[MoonBoi9001]

Sounds good, will update.

[tmigone]

@MoonBoi9001 sorry about this but can we use present-poi instead of present_poi? Just for consistency sake with other commands/sub-commands.

[MoonBoi9001]

Sounds good @tmigone see ac9cec3