fix(ci): fix Docker image organization

[youtalk]

Description

#4865 and #4961 mistakenly replaced parts of what should have been github.repository_owner with github.actor. As a result, the docker-build-and-push workflow is failing.

ERROR: failed to solve: failed to push ghcr.io/youtalk/autoware:20240717-autoware-universe-cuda-amd64: unexpected status from POST request to https://ghcr.io/v2/youtalk/autoware/blobs/uploads/: 403 Forbidden

https://github.com/autowarefoundation/autoware/actions/runs/9969218788/job/27545808443#step:5:9436

This PR reverts those changes.

https://github.com/autowarefoundation/autoware/actions/runs/9974064666

Effects on system behavior

Not applicable.

Interface changes

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[xmfcx]

Is it possible to tag this branch to see if docker build and push can build and push the image? Once it pushes the image, we can merge it.

[youtalk]

@xmfcx Please hold on an hour https://github.com/autowarefoundation/autoware/actions/runs/9974064666.

[youtalk]

Oh, it was failed due to another reason...
From my several months experience, docker/bake-action, which is used in docker-build-and-push workflow, tends to cause more problems than docker/build-push-action, which is used in health-check workflow. I will invalidate the relevant cache.

https://github.com/autowarefoundation/autoware/actions/runs/9974064666/job/27560776559#step:5:10093

105.1 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to lock apt for exclusive operation: Failed to lock directory /var/lib/apt/lists/: E:Could not open lock file /var/lib/apt/lists/lock - open (2: No such file or directory)"}

[youtalk]

@xmfcx I am continuing to address the issue where the docker-build-and-push fails due to disk space problems in subsequent PRs #5004 and #5005, but I want to merge this PR first as it is just a bug fix.