fix: remove --disable-content-trust push flag

[p5]

I do not believe this flag is necessary. If someone knows the origin of this, and we still need it, happy to close this PR.

When transferring data among networked systems, trust is a central concern. In particular, when communicating over an untrusted medium such as the internet, it is critical to ensure the integrity and the publisher of all the data a system operates on. You use Docker Engine to push and pull images (data) to a public or private registry. Content trust gives you the ability to verify both the integrity and the publisher of all the data received from a registry over any channel.

[castrojo]

I see we have this in the main repo and probably others as well. I don't recall why this is in there but looks like the toolboxes built just fine without it? Let's see how the push ends up?

[p5]

I see we have this in the main repo and probably others as well. I don't recall why this is in there but looks like the toolboxes built just fine without it? Let's see how the push ends up?

Yeah, my private repos work without this flag when pushing to GHCR, so I don't believe it's necessary.
Let's trial it here to reduce the impact if it goes wrong before changing main images

[p5]

CC @ublue-os/approver
If possible, can we also try and bundle this change into the Just PRs that are getting pushed through today.

It's removing the following from all workflows:

          extra-args: |
            --disable-content-trust