feat(cloudevents-server): append tail logs for failed steps

[wuhuizuo]

Signed-off-by: wuhuizuo wuhuizuo@126.com

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

The Pull Request introduces a new feature to the cloudevents-server where it appends tail logs for failed steps in the CI/CD pipeline.

Key Changes:

1. The Tekton struct in config.go has been extended to include a new field: FailedStepTailLines.
2. The handler.go file has been modified to include functionality for handling tail logs for failed steps.
3. The handler_pipelinerun.go and handler_taskrun.go files have been modified to extract information from event logs and handle cases where no receivers are found.
4. The lark.go file has been modified to include functions for composing and sending Lark messages.
5. The tekton-run-notify.yaml.tmpl file has been modified to include logs in the notification message.
6. The types.go file has been modified to include a new type stepInfo to store step related information including logs.
7. The newly added function getStepLog in handler.go retrieves the step logs.

Potential Problems:

1. There is no error handling for the function getStepLog. It can potentially fail if there is a problem with the HTTP request or if the response body cannot be read.
2. The logs fetched from getStepLog are dumped into the message directly without any formatting or checks. If the log contains sensitive information or is too large, it may cause issues.
3. The function getStepLog uses a GET request to fetch logs. If the logs are large, this might not be the best approach.
4. There are no tests included in this PR to verify the new feature.

Suggestions for Fixes:

1. Add error handling for the getStepLog function to ensure that errors are caught and handled appropriately.
2. Consider sanitizing or formatting the logs before adding them to the message.
3. Consider using a POST request or streaming the logs if they are expected to be large.
4. Include tests to verify that the feature works as expected and does not break existing functionality.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cloudevents-server/OWNERS [wuhuizuo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment