Fix for nested runtimes still using the relative url

[tofarr]

• This change is worth documenting at https://docs.all-hands.dev/
• Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

End-user friendly description of the problem this fixes or functionality this introduces.
When using nested runtimes, we were not updating the active conversation when the status changed, resulting in the url still being null, and defaulting to /conversations/{conversation_id} rather than the actual url

---

Summarize what the PR does, explaining any non-trivial design decisions.

I also removed a flaky test - before yesterday it had mocks in there and tested our code - but with the MCP migration it...

• Does not actually test our code (Since the timeout function is in the dependency)
• Uses external network (So is not really a unit test)
• Is flaky.

---

Link of any specific issues this addresses:

---

To run this PR locally, use the following command:

docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:bfd13f5-nikolaik   --name openhands-app-bfd13f5   docker.all-hands.dev/all-hands-ai/openhands:bfd13f5

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • Run Python Unit Tests

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #8947

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}

[malhotra5]

Thank you!