[improve][build] Upgrade docker-maven-plugin to 0.45.0

[nodece]

Motivation

docker-maven-plugin keeps up to the latest version.

Modifications

• Improve docker-push profile
• Remove tag goal, because build goal includes tag feature
• Upgrade docker-maven-plugin to 0.45.0

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

[lhotari]

@nodece does this make #22754 and #22609 obsolete? Please close them in that case.

I forgot the reason why the tag goal is removed. please add a description.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.45%. Comparing base (bbc6224) to head (202a701).
Report is 471 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #23091      +/-   ##
============================================
- Coverage     73.57%   73.45%   -0.13%     
- Complexity    32624    33511     +887     
============================================
  Files          1877     1917      +40     
  Lines        139502   144067    +4565     
  Branches      15299    15741     +442     
============================================
+ Hits         102638   105818    +3180     
- Misses        28908    30125    +1217     
- Partials       7956     8124     +168     

Flag	Coverage Δ
inttests	27.51% <ø> (+2.92%)	⬆️
systests	24.80% <ø> (+0.47%)	⬆️
unittests	72.51% <ø> (-0.33%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 513 files with indirect coverage changes

[nodece]

@lhotari Thanks, Done.

[lhotari]

LGTM

[lhotari]

@nodece One of the problems with the profile refactoring is that it breaks the current release process documented at https://pulsar.apache.org/contribute/release-process/#release-pulsar-30-and-later. I think that it would be better to revert the changes related to moving the profile to docker/pom.xml since many might have internal releases that break as a result.

[nodece]

If we push the image in the docker/pulsar or docker/pulsar-all directory, this PR will break the release process, otherwise, it works fine in the docker directory.

Usually, we will push images in the docker directory, what do you think?

[lhotari]

If we push the image in the docker/pulsar or docker/pulsar-all directory, this PR will break the release process, otherwise, it works fine in the docker directory.

Usually, we will push images in the docker directory, what do you think?

well, the release process uses -pl docker/pulsar,docker/pulsar-all. It will break. Many others might have copied the similar command that is used in https://pulsar.apache.org/contribute/release-process/#release-pulsar-30-and-later .

[nodece]

@lhotari #23093 will fix that.