feat: enabling e2e tests

[darrenvechain]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Go Version:
• Hardware:
• Docker Version:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• New and existing E2E tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have not added any vulnerable dependencies to my code

---

PR-Codex overview

This PR adds E2E tests for the Thor project and includes a new workflow for running these tests.

Detailed summary

• Added E2E tests for the Thor project.
• Created a new workflow (test-e2e.yaml) for running the E2E tests.
• The workflow builds a Docker image, runs the tests, and publishes the test results.
• The E2E tests are written in TypeScript and located in the tests/thor-e2e-tests directory.
• The E2E tests require Docker, Node.js, Yarn, and Git to be installed.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}