fix(docker): remove build main action

[oguzkaganozt]

Description

To simplify CI-CD pipeline ,build-main and build-main-self-hosted can be deleted because they are simply using the same docker build mechanism as docker-build-main and docker-build-main-self-hosted.

Also renaming of:

• docker-build-and-push-main -> docker-build-main
• docker-build-and-push-main-self-hosted -> docker-build-main-self-hosted

can be done since docker builds does not pushes every time into the registry the naming implies false positive.

Tests performed

Not applicable.

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.

[youtalk]

We are using docker-build-and-push-main and docker-build-and-push-main-self-hosted for not only main branch but also the other branches.
So are docker-build and docker-build-self-hosted better?

[xmfcx]

Please keep in mind that build-main runs every day. And docker-build-and-push-main runs twice a month.

build-main is necessary to keep track of the entire health of the autoware.

Also used in the README:

autoware/README.md

Lines 34 to 36 in 27e31e9

	<a href="https://github.com/autowarefoundation/autoware/actions/workflows/build-main.yaml?query=branch%3Amain">
	<img src="https://img.shields.io/github/actions/workflow/status/autowarefoundation/autoware/build-main.yaml?style=flat&label=build-main"
	alt="Build Main CI" /></a>

You may remove it but you also need to provide a way to:

• Build and test entire autoware every day
• Show the status in readme file.

[youtalk]

@oguzkaganozt I think this PR is important for the workflow refactoring, so I took over and made the necessary modifications.

@xmfcx I've updated the schedule to every day and the README badge. Note that there is no docker-build workflow until this PR is merged, so no badge has been generated.
Please review again.

[xmfcx]

But now the question is, do we want to update the base image and push it to registry every day?

I think there was a reason to do this twice a month. @mitsudome-r @youtalk

[youtalk]

Oh, I finally understood. The difference between build-main and docker-build-and-push-main is allow-push option.
That's why it might not be suitable to run docker-build-and-push-main every day.
@xmfcx I think so.

[oguzkaganozt]

@xmfcx @youtalk @mitsudome-r

Updated the PR so that; we are now using docker-build and docker-build-self-hosted both for daily builds and pushing images to registry twice a month. Please review again.

[youtalk]

@oguzkaganozt I'm sorry to review late.

Simplifying the workflow is a very good thing.
However, there is a constraint that unless we execute the docker-build action called in the build-main and build-main-self-hosted workflows, we cannot save the cache of docker build's --mount=type=cache cache to the GitHub Actions cache.
#4865

This might be fixed in a future update of buildkit-cache-dance action, but removing it now would mean disabling the ccache, resulting in CI build times becoming several times slower again.