Add an e2e test to verify the --comm option works fine

[hengyoush]

Is your feature request related to a problem? Please describe.
Add an e2e test to verify the --comm (filter by process name) option works fine

Describe the solution you'd like

1. Add a bash script file in testdata/ which contains the main test logic. (like this one: test_docker_filter_by_pid.sh), including two cases:

   1. target process start , then kyanos start , expected kyanos can watch the target process's network.
   2. kyanos start, then target process start, expected kyanos can watch the target process's network.

2. Add a step in workflow : .github/workflows/test.yml which executes the test script file in 1.

[spencercjh]

Can a simple Python HTTP server be started directly (not in a Docker container) in this e2e test?

sudo ./kyanos watch -d http --comm python3

I need to simulate my local operation in the test.

AM I RIGHT?

[spencercjh]

You haven't started this work yet, have you?

[hengyoush]

You haven't started this work yet, have you?

No, I haven't.

Can a simple Python HTTP server be started directly (not in a Docker container) in this e2e test?

ok.

@spencercjh Thank you very much, assigned this issue to you.