Added empty build.gradle files for arm64 and s390x because the gradle assemble task fails without them

[evankielley]

Description

This change fixes the gradle assemble task which is failing due to missing build.gradle files in the docker subprojects for arm64 and s390x. These files were removed in PR #4723. I created issue #8903 to discuss this particular bug and created this PR for a quick fix. In addition, issue #8112 was created to further investigate why removing those files causes the build to fail.

Related Issues

Resolves #8903
Related #8112

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/21033/
• CommitID: b7804fd
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/21037/
• CommitID: 1e368ed
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[reta]

@evankielley could you please rebase against latest main (to fix build issues)? Also, thanks to you finding, I will suggest to add distribution checks for pull requests (#8924), that would have caught the issue ... thank you

[evankielley]

@evankielley could you please rebase against latest main (to fix build issues)? Also, thanks to you finding, I will suggest to add distribution checks for pull requests (#8924), that would have caught the issue ... thank you

@reta I just rebased but as for adding a distro check to gradle assemble, it looks like you have that covered now in PR #8924 ?

[reta]

@reta I just rebased but as for adding a distro check to gradle assemble, it looks like you have that covered now in PR #8924 ?

Thanks @evankielley , I temporarily applied your fix (to prove that all checks pass) but it is removed. I will rebase the my change after we get this one in, thank you.

[evankielley]

@reta I just rebased but as for adding a distro check to gradle assemble, it looks like you have that covered now in PR #8924 ?

Thanks @evankielley , I temporarily applied your fix (to prove that all checks pass) but it is removed. I will rebase the my change after we get this one in, thank you.

Perfect, thank you

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/21190/
• CommitID: b34224d
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testStartReplicaAfterPrimaryIndexesDocs

• URL: https://build.ci.opensearch.org/job/gradle-check/21191/
• CommitID: b34224d
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

Merging #8904 (b34224d) into main (5495c64) will increase coverage by 0.40%.
Report is 6 commits behind head on main.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #8904      +/-   ##
============================================
+ Coverage     71.08%   71.49%   +0.40%     
- Complexity    57276    57552     +276     
============================================
  Files          4758     4758              
  Lines        269869   269869              
  Branches      39487    39487              
============================================
+ Hits         191836   192930    +1094     
+ Misses        61891    61054     -837     
+ Partials      16142    15885     -257     

see 436 files with indirect coverage changes

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/21198/
• CommitID: b34224d
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/21204/
• CommitID: b34224d
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/21212/
• CommitID: b34224d
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/21257/
• CommitID: b34224d
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.client.PitIT.testDeleteAllAndListAllPits

• URL: https://build.ci.opensearch.org/job/gradle-check/21261/
• CommitID: b34224d
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.