fix: nested loop agents escalation issue

[nx90]

In nested loop agents scenario, the event.action.escalate will break all loop agents, the expected behavior should be only break one level of the loop agents.

Issue link: #526

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Jacksunwei]

Actually I think the action should not be changed. We should check whether there is no another loop agent between the current agent and the event author.

[Jacksunwei]

We should instead check whether this is no more loop agent between this agent and the event author agent.

---

event.actions.escalate is the conversation history and we shouldn't alter it.

[Jacksunwei]

@selcukgun could you take over and finish this PR?

[ryanaiagent]

Hi @nx90 and thanks to everyone who participated in this thread.

We're currently doing some housekeeping on our pull request queue. Given the rapid pace of development and the number of updates since this was last active, there's a good chance this pull request needs to be caught up to the latest version. To help us keep our backlog focused on current pull requests, we are closing this as stale.

If you're still interested in contributing to this change, could you please update to the very latest version of the library and create a new pull request? Our team will be glad to help with the refreshed PRs and answer any questions!

Thanks for your contribution and understanding!