chore: remove arch path in single image build

[iutx]

What this PR does / why we need it:

Remove arch path in single image build.

Build a single-architecture image without the need for an additional layer of identification; this approach may be utilized in the development environment. For multi-architecture scenarios, utilize buildx.

Which issue(s) this PR fixes:

• Fixes #your-issue_number
• [Erda Cloud Issue Link](paste your link here)

Specified Reviewers:

/assign @sfwn

ChangeLog

Language	Changelog
🇺🇸 English	remove arch path in single image build
🇨🇳 中文	单架构构建移除 arch 路径

Need cherry-pick to release versions?

Add comment like /cherry-pick release/1.0 when this PR is merged.

For details on the cherry pick process, see the cherry pick requests section under CONTRIBUTING.md.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (36e0f90) 22.69% compared to head (2e1e172) 22.66%.
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6254      +/-   ##
==========================================
- Coverage   22.69%   22.66%   -0.03%     
==========================================
  Files        1833     1833              
  Lines      196231   196255      +24     
==========================================
- Hits        44526    44484      -42     
- Misses     146591   146668      +77     
+ Partials     5114     5103      -11     

see 8 files with indirect coverage changes

[sfwn]

We use this arch-in-path to clearly state that this is a single architecture image to prevent it from being mistaken as a multi-architecture image.

[iutx]

We use this arch-in-path to clearly state that this is a single architecture image to prevent it from being mistaken as a multi-architecture image.

In the development process, pushing paths exceeding two levels is not allowed in non-enterprise repositories.
Would it be more reasonable to use tags to identify the architecture?

[sfwn]

We use this arch-in-path to clearly state that this is a single architecture image to prevent it from being mistaken as a multi-architecture image.

In the development process, pushing paths exceeding two levels is not allowed in non-enterprise repositories. Would it be more reasonable to use tags to identify the architecture?

ok, please do so.

[iutx]

We use this arch-in-path to clearly state that this is a single architecture image to prevent it from being mistaken as a multi-architecture image.

In the development process, pushing paths exceeding two levels is not allowed in non-enterprise repositories. Would it be more reasonable to use tags to identify the architecture?

ok, please do so.

Done. Please review the code.

[sfwn]

/approve