[Hexagon]: Add upload function to hexagon session

[mehrdadh]

This PR adds upload to hexagon RPC server running on Hexagon side. This will remove the need of adb command for uploading/executing binary files on hexagon.

[tvm-bot]

Thanks for contributing to TVM! Please refer to the contributing guidelines https://tvm.apache.org/docs/contribute/ for useful information and tips. Please request code reviews from Reviewers by @-ing them in a comment.

• No users to tag found in teams: hexagon _{See #10317 for details}
• Built docs for commit 7f29069 can be found here.

_{Generated by tvm-bot}

[Lunderberg]

I like the session-scoped uploads, and allowing tests to be reliant solely on the hexagon_session instead of the hexagon_launcher. This is a strictly better usage for a testing environment, where all state should be session-scoped. However, it doesn't allow for a production use case in which a model is uploaded once, and then run many times across many connections.

I'd propose the following design, which would allow for both use cases:

• A HexagonSession has a single workspace, which should be cleared when closing a session. Calls to HexagonSession.upload go into that session's workspace. Calls to HexagonSession.load_module may only be a tvm.runtime.Module, and not a str or pathlib.Path, because persistent uploads are not supported.
• A HexagonLauncher has a single workspace, which should be persistent across multiple connections to the same device. Calls to HexagonLauncher.upload go into the persistent workspace. Calls to HexagonLauncher.load_module may be a tvm.runtime.Module, or a str/pathlib.Path to access previously uploaded artifacts.

This would be simplest to implement by having a upload method in both HexagonLauncher and HexagonSession. Each would call a private method of HexagonLauncher that takes an explicit workspace, but those workspaces would not otherwise be exposed to the user.

[Lunderberg]

Thank you, and the changes made address all the specific changes requested. I think the last item remaining is how the new design would support persistent artifacts stored on the hexagon device across multiple sessions.

[Lunderberg]

Following conversation with @mehrdadh , support for persistence across sessions to be re-added in a follow-up PR.