fix(agents): make invocations_ws protocol priority order-independent in loadServiceProtocol

[Copilot]

loadServiceProtocol returned invocations_ws immediately on match, making protocol selection order-dependent: --protocol invocations_ws --protocol responses classified the agent as WebSocket-only (suppressing invoke hints), while the reversed order correctly returned responses.

Changes

• nextstep/state.go: Replace the early return ProtocolInvocationsWS with a sawInvocationsWS tracking variable (mirroring the existing sawInvocations pattern). Priority is now order-independent: responses > invocations > invocations_ws. Updated doc comment to reflect the full priority chain.

• nextstep/state_test.go: Two regression cases covering the reversed-order scenarios:

  • invocations_ws declared before responses → still returns responses
  • invocations_ws declared before invocations → still returns invocations

// Before — order-dependent
case ProtocolInvocationsWS:
    return ProtocolInvocationsWS  // wins if listed first

// After — order-independent
case ProtocolInvocationsWS:
    sawInvocationsWS = true       // only wins if no azd-invocable protocol present

[azure-pipelines]

Azure Pipelines:
20 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.