feat: Refactor release process for bundling

This change refactors the release process to support a new bundle-based publishing method while
maintaining backward compatibility for existing release and patch workflows.

Key changes:
- The  composite action now includes a  input (string, default 'false') to conditionally switch between the old source-based publishing
the new bundle-based method.
- The  workflow is updated to use the new bundle-based process ().
- The  workflow includes a new  input (defaulting to false) to allow for manual testing of either release method.
- Existing  and patch workflows remain unchanged, ensuring they continue to use the old, non-bundled process for backward compatibility.

.github/workflows/release-manual.yml

@@ -36,6 +36,11 @@ on:
         required: false
         type: 'boolean'
         default: false
+      use_bundle_release:
+        description: 'Use the new bundle-based release process.'
+        required: true
+        type: 'boolean'
+        default: false
       environment:
         description: 'Environment'
         required: false
@@ -121,6 +126,7 @@ jobs:
           cli-package-name: '${{ vars.CLI_PACKAGE_NAME }}'
           core-package-name: '${{ vars.CORE_PACKAGE_NAME }}'
           a2a-package-name: '${{ vars.A2A_PACKAGE_NAME }}'
+          use-bundle-release: '${{ github.event.inputs.use_bundle_release }}'
 
       - name: 'Create Issue on Failure'
         if: '${{ failure() && github.event.inputs.dry_run == false }}'

.github/workflows/release-nightly.yml

@@ -135,6 +135,7 @@ jobs:
           cli-package-name: '${{ vars.CLI_PACKAGE_NAME }}'
           core-package-name: '${{ vars.CORE_PACKAGE_NAME }}'
           a2a-package-name: '${{ vars.A2A_PACKAGE_NAME }}'
+          use-bundle-release: 'true'
 
       - name: 'Create and Merge Pull Request'
         if: "github.event.inputs.environment != 'dev'"