fix: widen ActorSelection SendConsistencySpec timeout to 60s

[He-Pin]

Motivation

The "must be able to send messages with actorSelection concurrently preserving order" test flakes on CI: 4 sender actors each drive 1000 round trips via ActorSelection (4004 messages total), wrapped in ActorSelectionMessage with remote-side path traversal overhead. On CI with -Dpekko.test.timefactor=2, within(30.seconds) dilates to 60s which is insufficient under load — 3 of 4 senders complete but the 4th times out waiting for the final success2 message.

Investigation confirmed no recent code change caused this:

• Artery does not use stage actors → LazyDispatch (ba4e950) has zero impact
• Materializer wiring optimization (03ebaf5) affects materialization only, not runtime message flow
• GraphInterpreter pendingFinalization (a505843) is a hot-path optimization, no behavioral change

Modification

Bump within(30.seconds) → within(60.seconds) at line 219 for the ActorSelection test only. The ActorRef variant (line 179) is unchanged as it passes within the original budget.

Result

Up to 120s of dilated wall-clock headroom on CI for the ActorSelection variant; still fails fast on genuine deadlocks.

Tests

• sbt "remote / Test / compile" — passes
• CI Check / Test will exercise the artery variants

References

Refs #3041 (previous timeout widening from 10s to 30s)

[pjfanning]

test now failing in scala 3.3

[He-Pin]

Closing in favor of #3092 which fixes the root cause.

The timeout widening only masks the symptom. The actual issue is that selectQueue in Association.send uses the anchor's UID (root guardian, always 0) as the distribution key for outbound lanes. With outbound-lanes > 1, all ActorSelection messages concentrate on a single lane (math.abs(0 % N) = 0), creating a throughput bottleneck.

#3092 distributes ActorSelection messages across lanes based on their target path hash instead, eliminating the structural bottleneck.