Remove Pom task dependenices rewrite

[peternied]

Description

The underlying issue associated with Pom validation was fixed in OpenSearch [1], this causes the 'hack' that was used to unblock pom generation in security to start causing problems in the distribution builds.

• [1] Add explicit dependency to validatePom and generatePom tasks. OpenSearch#12807

Issues Resolved

• Fixes [AUTOCUT] Distribution Build Failed for security-3.0.0 #4160

Testing

Added new CI test that executes the same job used by the distribution build and checks the expected artifacts exist

Check List

• New functionality includes testing
• New functionality has been documented
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.93%. Comparing base (551d026) to head (c67e6d4).

❗ Current head c67e6d4 differs from pull request most recent head a11f30e. Consider uploading reports for the commit a11f30e to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4178      +/-   ##
==========================================
+ Coverage   65.90%   65.93%   +0.02%     
==========================================
  Files         298      298              
  Lines       21425    21425              
  Branches     3475     3475              
==========================================
+ Hits        14121    14126       +5     
+ Misses       5563     5557       -6     
- Partials     1741     1742       +1     

see 1 file with indirect coverage changes

[cwperks]

@peternied Does this need to be backported?

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/security/backport-2.x
# Create a new branch
git switch --create backport/backport-4178-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 dc8bd61a8df01b32805ddde0b6f6c6010eeca5cf
# Push it to GitHub
git push --set-upstream origin backport/backport-4178-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-4178-to-2.x.