Fix Error by given linters during tests

[khrm]

Fix error given by revive linter either by commenting if it can't be fixed or fixing the issue.

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices
• Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Release Notes

NONE

[khrm]

/kind misc

[khrm]

/release-note-none

[tekton-robot]

@khrm: you can only set the release note label to release-note-none if the release-note block in the PR body text is empty or "none".

In response to this:

/release-note-none

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-triggers-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/interceptors/server/server.go	78.9%	79.7%	0.8

[khrm]

/test tekton-triggers-unit-tests

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-triggers-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/interceptors/server/server.go	78.9%	79.7%	0.8

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-triggers-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/interceptors/server/server.go	78.9%	79.7%	0.8

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-triggers-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/interceptors/server/server.go	78.9%	79.7%	0.8
pkg/reconciler/eventlistener/resources/custom.go	93.8%	93.8%	-0.1

[khrm]

@dibyom Please merge this to resolve the latest CI issue with the build test failure.

[dibyom]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

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:

• OWNERS [dibyom]

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

[khrm]

/cherry-pick release-v0.22.x

[tekton-robot]

@khrm: #1578 failed to apply on top of branch "release-v0.22.x":

Applying: Fix Error by revive linter for build tests
Using index info to reconstruct a base tree...
M	pkg/apis/triggers/v1beta1/event_listener_validation.go
M	pkg/apis/triggers/v1beta1/trigger_binding_validation.go
M	pkg/apis/triggers/v1beta1/trigger_template_validation.go
M	pkg/apis/triggers/v1beta1/trigger_validation.go
M	pkg/interceptors/server/server_test.go
M	pkg/sink/sink_test.go
M	test/eventlistener_test.go
M	test/wait.go
Falling back to patching base and 3-way merge...
Auto-merging test/wait.go
Auto-merging test/eventlistener_test.go
Auto-merging pkg/sink/sink_test.go
Auto-merging pkg/interceptors/server/server_test.go
Auto-merging pkg/apis/triggers/v1beta1/trigger_validation.go
Auto-merging pkg/apis/triggers/v1beta1/trigger_template_validation.go
Auto-merging pkg/apis/triggers/v1beta1/trigger_binding_validation.go
Auto-merging pkg/apis/triggers/v1beta1/event_listener_validation.go
CONFLICT (content): Merge conflict in pkg/apis/triggers/v1beta1/event_listener_validation.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix Error by revive linter for build tests
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-v0.22.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.