Fix two bugs in RPCIndividual

[LautaroPetaccio]

Two bugs in RPCIndividual, both found while writing an equivalent individual for another problem type and copying this one's shape. Independent of that work, so sent on its own.

seeIndexedRPCCalls always returns an empty map

funseeIndexedRPCCalls(): Map<Int, RPCCallAction> = getIndexedChildren(RPCCallAction::class.java)

getIndexedChildren filters the individual's direct children by type, but the calls are not direct children: the constructor wraps each in an EnterpriseActionGroup, alongside the external-service actions belonging to it. So nothing ever matches the filter and the result is always empty.

Compare RestIndividual.getIndexedResourceCalls, which works because RestResourceCalls really is the child type there.

The method has no callers today, which is presumably why it went unnoticed. The fix unwraps the group.

The convenience constructor throws whenever it is used without external services

addAll(actions.mapIndexed { index, rpcCallAction ->if (externalServicesActions.isNotEmpty()){
Lazy.assert { actions.size == externalServicesActions.size }
}
EnterpriseActionGroup(...).apply {
addChildrenToGroup(externalServicesActions[index], ...) // <- not guarded
}})

externalServicesActions defaults to an empty list. The isNotEmpty() check guards only the assert; the indexing right after it is unguarded, so externalServicesActions[index] throws IndexOutOfBoundsException on the very first call.

In practice only callers passing a list of matching size work — which is what EvaluatedIndividualBuilder.buildEvaluatedRPCIndividual does, so the existing tests never hit it. Constructing an RPCIndividual the way the default parameters invite you to fails immediately.

The fix adds the missing bound check, leaving behaviour unchanged when a list is supplied.

Testing

Adds RPCIndividualTest, which the class had none of — four tests covering the indexed lookup, the indices actually addressing the children that hold the calls, calls found past initializing actions, and the empty case. The first of them fails on both bugs before the fix.

RPCActionNamingStrategyTest, TestSuiteWriterRPCTest and TestSuiteOrganizerTest still pass.

[arcuri82]

hi @LautaroPetaccio thx!
as this is about RPC support, @man-zhang can you look at this PR once you are back from vacation? txh!