Preserve intermediate released build artifacts perminately

[peternied]

Related to #787

There are two environments for build artifacts and the location of these artifacts have shifted as improvements have been made. In order to ensure we can patch previous releases we need to keep intermediate artifacts where they will be safe/consist as part of a post release process.

Acceptance Criteria

• design a process for storing all artifacts and logs from a distribution build workflow
  • include the Jenkins job log
  • should capture everything in S3 associated with that build
  • needs to be accessible without S3
• create a job that give a job name, build num, s3 path, will copy everything
• update the release process to include this job
• run this job on all previous releases

[zelinh]

[Triage] @peternied Could you provide more details to this task?

[peternied]

Updated with much additional detail

[bbarani]

@opensearch-project/engineering-effectiveness Please provide an update.

[peterzhuamazon]

All the build artifacts are now in S3, but build log is directly associate with Jenkins.
We can use the build number to find the build log.

Thanks.

[bbarani]

Closing this issue based on @peterzhuamazon comment.