fix: make strict rules on amd64 experimental builds

[Bidon15]

Overview

Closes https://github.com/celestiaorg/devops/issues/527

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

[tty47]

LGTM

[MSevey]

In general I don't understand why we are doing this change. The linked issue points to a problem with arm builds but this change is impact the amd images.

Additionally this is just limiting what triggers the builds but does nothing to change the image itself which is what the issue is related to.

Please provide additional context to why we are doing this change.

[Bidon15]

In general I don't understand why we are doing this change. The linked issue points to a problem with arm builds but this change is impact the amd images.

Additionally this is just limiting what triggers the builds but does nothing to change the image itself which is what the issue is related to.

Please take a look here:
https://github.com/celestiaorg/celestia-node/actions/runs/6458347843/job/17532066994

This is a job that was building the main branch. As you can see the amd64 shouldn't build 1 image twice in 2 jobs.
We need to remove this effect to make sure it's not the root cause of the issues we see with amd64 being marked as arm64

[smuu]

One comment, otherwise LGTM

[smuu]

This means it does not build on a fork, which should happen, to report back an error to the developer if something breaks.
Building it always and only pushing on non-forks results in that behavior.

[MSevey]

closing in favor off #77