vm/adb: allow to run complex script with device|console info

[jiangenj]

---

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

---

[a-nogikh]

Hi Joey!
This PR completely changes the semantics of the RepairScript parameter - it used to be the name of the local file containing the script, now it's the script body itself / the name of the file on the device. Is that change really necessary?

The second change (vm/adb: pass device|console info to script) looks good to me.

[jiangenj]

it used to be the name of the local file containing the script, now it's the script body itself / the name of the file on the

Hi @a-nogikh , RepairScript accepts script file only, even with the change, it is still using the script filename only.

The difference between sh -c content and sh script can sometimes cause confusion due to how they handle commands and scripts.

sh -c content: This command runs the string content as a shell command. If content contains multiple commands or special characters, it might need proper quoting or escaping. For example, sh -c "echo Hello; echo World" works, but sh -c echo Hello; echo World will not because the shell interprets echo Hello; as a separate command.

sh script: This command runs the script file named script. The script file can contain multiple lines of commands, and the shell will execute them sequentially. This method is generally more straightforward as it doesn't require special handling of quotes or escaping within the script.

[a-nogikh]

Ah, I see, the script is anyway executed on the host side. Thanks for the clarification.