Remove unused workflow that publishes new images to docker hub

[jrakas-dev]

What is this PR about? / Why do we need it?
We no longer need this workflow that pushes images to Docker Hub (we now host images in ECR), so this PR removes it.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jrakas-dev
Once this PR has been reviewed and has the lgtm label, please assign d-nishi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @jrakas-dev. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[dankova22]

/ok-to-test

[k8s-ci-robot]

@dankova22: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/ok-to-test

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-sigs/prow repository.

[dankova22]

/ok-to-test

[k8s-ci-robot]

@dankova22: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/ok-to-test

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-sigs/prow repository.

[dankova22]

/ok-to-test

[dankova22]

/retest

[jrakas-dev]

/retest

[k8s-ci-robot]

@jrakas-dev: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-aws-efs-csi-driver-verify	b9369b7	link	true	/test pull-aws-efs-csi-driver-verify
pull-aws-efs-csi-driver-unit	b9369b7	link	true	/test pull-aws-efs-csi-driver-unit
pull-aws-efs-csi-driver-e2e	b9369b7	link	true	/test pull-aws-efs-csi-driver-e2e
pull-aws-efs-csi-driver-external-test-eks	b9369b7	link	true	/test pull-aws-efs-csi-driver-external-test-eks

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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-sigs/prow repository. I understand the commands that are listed here.