chore: test external push to protected branch

[ARR4N]

Important

Please DO NOT merge this via the GitHub UI!

Why this should be merged

Pushing this commit to the libevm branch fails (by design) because of branch protection requiring a PR. I want to test what happens if, once the PR is approved and all status checks pass, I locally git merge --ff-only on the libevm branch before pushing to GitHub. Will it recognise and honour the PR?

Without this, the GitHub PR merge uses --no-ff, which isn't always desirable as it introduces an extra merge commit when fast-forwarding was possible.

How this works

Empty commit that is a fast forward of the libevm branch.

How this was tested

n/a

[ARR4N]

This looks promising. I tried to push with CI running:

remote: error: GH013: Repository rule violations found for refs/heads/libevm.
remote: Review all repository rules at http://github.com/ava-labs/go-ethereum/rules?ref=refs%2Fheads%2Flibevm
remote: 
remote: - At least 1 approving review is required by reviewers with write access.
remote: 
remote: - Required status check "go_test_short" is in progress.
remote: 
To github.com:ava-labs/go-ethereum.git

And once it finished:

remote: error: GH013: Repository rule violations found for refs/heads/libevm.
remote: Review all repository rules at http://github.com/ava-labs/go-ethereum/rules?ref=refs%2Fheads%2Flibevm
remote: 
remote: - At least 1 approving review is required by reviewers with write access.
remote: 
To github.com:ava-labs/go-ethereum.git