This pull request updates the eng/ci/release.yml file to streamline artifact handling and simplify folder paths in the release pipeline configuration. The changes primarily focus on standardizing the artifact paths and ensuring consistency across multiple pipeline steps.

Artifact Path Updates:

• Updated the folderlocation paths to remove the _durabletask-java.official prefix, simplifying the directory structure for artifacts like durabletask-azuremanaged, durabletask-client, and durabletask-azure-functions. ([[1]](https://github.com/microsoft/durabletask-java/pull/220/files#diff-0b4964880447dddb515c7c134cb70a41bcf08f9fbea7b9bf1453a121e49ffda3L44-R46), [[2]](https://github.com/microsoft/durabletask-java/pull/220/files#diff-0b4964880447dddb515c7c134cb70a41bcf08f9fbea7b9bf1453a121e49ffda3L68-R71), [[3]](https://github.com/microsoft/durabletask-java/pull/220/files#diff-0b4964880447dddb515c7c134cb70a41bcf08f9fbea7b9bf1453a121e49ffda3L92-R96))

Pipeline Configuration Enhancements:

• Added targetPath to specify the target directory for pipeline artifacts as $(System.DefaultWorkingDirectory)/drop for multiple steps. ([[1]](https://github.com/microsoft/durabletask-java/pull/220/files#diff-0b4964880447dddb515c7c134cb70a41bcf08f9fbea7b9bf1453a121e49ffda3R35), [[2]](https://github.com/microsoft/durabletask-java/pull/220/files#diff-0b4964880447dddb515c7c134cb70a41bcf08f9fbea7b9bf1453a121e49ffda3R60), [[3]](https://github.com/microsoft/durabletask-java/pull/220/files#diff-0b4964880447dddb515c7c134cb70a41bcf08f9fbea7b9bf1453a121e49ffda3R85))
• Explicitly set the branch to main for the DurableTaskJavaBuildPipeline source, ensuring the pipeline operates on the correct branch. ([eng/ci/release.ymlR13](https://github.com/microsoft/durabletask-java/pull/220/files#diff-0b4964880447dddb515c7c134cb70a41bcf08f9fbea7b9bf1453a121e49ffda3R13))…ranch and adjust folder locations for artifacts

Issue describing the changes in this PR

resolves #issue_for_this_pr

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes are added to the CHANGELOG.md
• I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information