ci: add npm-publish workflow (#320)

*Issue #, if available:*

*Description of changes:* adding npm-publish Github Actions Workflow
that I tested in
#319. Since the
other branch is publishing an empty package, it's difficult to directly
merge from that branch. I've strictly copied over the required workflow
files. Prior to publishing our packages to npm we still need to change
the versions to 1.0.0.


By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.

Author: SilanHe

.github/workflows/iterate-publish-npm.sh

@@ -0,0 +1,11 @@
+#!/bin/bash
+
+for package_dir in packages/*; do
+  if [ -d "$package_dir" ] && [[ "$package_dir" == "packages/aws-durable-execution-sdk-js-testing" || "$package_dir" == "packages/aws-durable-execution-sdk-js" || "$package_dir" == "packages/aws-durable-execution-sdk-js-eslint-plugin" ]]; then
+    echo "$package_dir";
+    cd "$package_dir";
+    echo "Publishing package in $package_dir";
+    npm publish --access public;
+    cd ../..;
+  fi
+done

.github/workflows/npm-publish.yml

@@ -0,0 +1,28 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
+
+name: npm publish
+permissions:
+  contents: read
+on:
+  release:
+    types: [published]
+jobs:
+  npm-publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm run build
+      - run: npm run test
+      - name: Make script executable
+        run: chmod +x ./.github/workflows/iterate-publish-npm.sh
+      - name: iterate and publish
+        run: ./.github/workflows/iterate-publish-npm.sh
+        shell: bash
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}