ci: setup tests

[junhuif]

Type of change

• configuration
• test

Description

• Setup CI on GitHub Actions:
  • Run test, build.
  • Run example.

Related issues

#43.

Notes for reviewer

Deprecated the Prow CI after this PR is merged.

[Copilot]

Pull Request Overview

This PR sets up GitHub Actions CI workflows to replace the deprecated Prow CI system. The changes include creating automated testing and building pipelines, along with example integration testing.

• Added main CI workflow with Go testing, building, and vulnerability scanning
• Added example CI workflow for integration testing with Node.js dependencies
• Updated test expectations to use relative paths instead of full GitHub module paths

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/main.yml	Main CI pipeline with Go tests, build, and security checks
.github/workflows/example.yml	Example integration testing with Go and Node.js setup
trace/trace_test.go	Updated expected log paths to be relative for CI compatibility

[Copilot]

Running make rungo in the background without proper process management could leave orphaned processes. Consider adding a cleanup mechanism or using a more robust way to manage the background process lifecycle.

Suggested change

	make runjs
	make rungo &
	RUNGO_PID=$!
	make runjs
	kill $RUNGO_PID

[junhuif]

X-ref: https://theplanttokyo.atlassian.net/browse/MWMOP-4365?focusedCommentId=432207

I don’t plan to spend more time on this:

• Migrating CI from Prow to GitHub Actions is not necessary.
• Prottp currently depends on multiple Protobuf versions, causing unstable CI results.
• Fixing the multiple Protobuf dependency issue in Prottp would involve updating multiple repos, such as theplant/validator and other apps that depend on Prottp.
  • https://github.com/theplant/validator/blob/master/proto/spec.pb.go#L10