ci: Update publishing mechanism for npmjs

[rbarker-dev]

Description

This pull request updates the ATS publishing workflow to separate the packaging and publishing steps for both the contracts and SDK packages. It introduces new jobs for preparing and uploading package artifacts, and adds a dedicated job for publishing these artifacts to npm. Additionally, it updates package metadata and changelogs to reflect these workflow changes and the new version.

Workflow and Publishing Improvements:

• Refactored the .github/workflows/ats.publish.yml workflow to split the publishing process into three jobs: prepare-contracts, prepare-sdk, and publish-npm-packages. The new structure builds, packages, and uploads artifacts before a final job publishes them to npm, improving reliability and enabling provenance publishing for non-production releases. [1] [2] [3] [4]
• Added artifact upload and download steps using actions/upload-artifact and actions/download-artifact to pass built package files between jobs, ensuring only validated artifacts are published. [1] [2]
• Updated the summary reporting step to reflect the new job names and results, providing clearer feedback on each phase of the process.

Package Metadata and Versioning:

• Bumped the version of @hashgraph/asset-tokenization-contracts, @hashgraph/asset-tokenization-sdk, and @hashgraph/asset-tokenization-dapp to 1.17.1 and updated their package.json files to include the repository URL. [1] [2] [3]
• Updated changelogs for all three packages to document the workflow changes and new version. [1] [2] [3]

Type of change

• New feature ✨

Testing

Dry run publish ✅

[hedera-eng-infrastructure]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.