feat: prompt instructions for runtimes

[idagelic]

• 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 that this introduces.

Tells the agent which URLs to use when responding with links for reaching running apps on Daytona.

---

Give a summary of what the PR does, explaining any non-trivial design decisions.

This PR adds an additional_instructions property to runtimes which then gets forwarded to the PromptManager.
For Daytona, it is used to pass this message:

"When showing endpoints to access applications for any port, e.g. port 3000, instead of localhost:3000, use this format: .<workspace_id>.<node_domain>"

which shows the user a correct link to access the preview URL for a running application.

---

Link of any specific issues this addresses.

Discussed briefly in #6863

[enyst]

Sorry for being dense, what is the use case for deduce_all_web_hosts=False?

[idagelic]

This defaults to False because other runtimes might not allow exposing any port for serving applications and might only allow a fixed number of them which they defined in web_hosts.
For Daytona, we want to instruct the agent to change any occurance of "sending" the user to a port to send the user to our preview URL instead.

This was the way I tried interfacing the runtimes, but I since got a suggestion to just add a runtime_instructions property allowing runtimes to define any custom instructions they want. I'll update the PR soon

[enyst]

other runtimes might not allow exposing any port for serving applications

Then they can set the list of ports to an empty list, and the template will not display anything, right? I'm sorry, I still don't see why that needs an additional boolean, but I'm looking forward to the updates, don't worry about it.

[idagelic]

That's true, but if a runtime were to set web_hosts 3000 and 3001 -> localhost, and those were the only endpoints open for access, I believe asking the LLM to use port 6000 would still return "localhost:6000" if deduce_all_web_hosts were true, while in reality the runtime might not want the LLM to assume those ports as well

I pushed the new additional_instructions property - let me know whether you think I used proper naming