CI: deploy-wasm workflow does not run when core files are updated

[ChinYikMing]

The Wasm deployment only runs when following files are updated:

files: |
              assets/html/index.html
              assets/js/pre.js
              build/*.elf

Updates to the core C files should also initiate deployment, as these changes could gain performance. Additionally, several prebuilt ELF executables are stored in the rv32emu-prebuilt directory, and the current method for detecting changes in ELF files is less effective. It should be revised to monitor updates in the rv32emu-prebuilt repository.

[ChinYikMing]

To monitor rv32emu-prebuilt, I invert the dependency. Specifically, when a release is published in rv32emu-prebuilt, it triggers a repository_dispatch event. This release event leverages GitHub REST APIs to send a workflow payload to rv32emu whereas rv32emu listens for the repository_dispatch event and deploy the wasm. In this way, we can monitor any update of ELF or Linux image.

The example of using curl command to send the workflow payload:

curl -X POST \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <PAT_with_workflow_permission>" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/repos/sysprog21/rv32emu/dispatches \
  -d '{"event_type": "test_result", "client_payload": {"passed": false, "message": "Error: timeout"}}'