Don't append :443 to registry domain in the kubernetes-worker layer registry action

[jacekn]

What this PR does / why we need it: Fixes #45547

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #45547

Special notes for your reviewer:

Release note:

Fix #45547 - don't append :443 to juju created docker registry config

[k8s-ci-robot]

Hi @jacekn. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with @k8s-bot 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.

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

[k8s-reviewable]

This change is 

[lazypower]

/assign @chuckbutler

[lazypower]

@k8s-bot ok to test

[lazypower]

@k8s-bot kops aws e2e test this

[lazypower]

/approve

[lazypower]

/lgtm

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chuckbutler, jacekn

Needs approval from an approver in each of these OWNERS Files:

• cluster/juju/OWNERS [chuckbutler]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 45569, 45602, 45604, 45478, 45550)