Revert pull_request action back about abris

[cerveada]

Another idea that could help with this is to split tests and test coverage in separated actions.

• Tests don't need the write permission at all and can happily run using pull_request
• Test coverage require the permission, but even if it fails, we can still asses the amount of new untested code easily. Adding to that - external PRs are usually small, so it's even less of a problem.

[kevinwallimann]

pull_request_target doesn't work like we think. It "runs in the context of the base of the pull request", so it doesn't actually run with the changes from the pull request. It may be useful for tasks like auto-labeling issues, but not to run the build of the PR. It is not a drop-in replacement for pull_request

[cerveada]

In #339 we reverted to using pull_request and separated the workflows for tests and test coverage.