Fix nested workflow calls to use absolute paths

Changed relative paths (./.github/workflows/package.yml) to absolute
repository paths (salesforcecli/github-workflows/.github/workflows/vscode-package.yml@feat/add-vscode-extension-ci)

This fixes the issue where reusable workflows called from other repos
would fail with 'workflow was not found' errors because relative paths
resolve to the calling repo, not the workflow's repo.

Author: madhur310

.github/workflows/vscode-ci-template.yml

@@ -165,7 +165,7 @@ jobs:
     name: Package
     needs: test
     if: ${{ needs.test.result == 'success' }}
-    uses: ./.github/workflows/package.yml
+    uses: salesforcecli/github-workflows/.github/workflows/vscode-package.yml@feat/add-vscode-extension-ci
     with:
       branch: ${{ github.head_ref || github.ref_name }}
       artifact-name: vsix-packages

.github/workflows/vscode-publish-extensions.yml

@@ -261,7 +261,7 @@ jobs:
 
   package:
     needs: [bump-versions, calculate-artifact-name, determine-changes]
-    uses: ./.github/workflows/package.yml
+    uses: salesforcecli/github-workflows/.github/workflows/vscode-package.yml@feat/add-vscode-extension-ci
     with:
       branch: ${{ inputs.branch || github.ref_name }}
       artifact-name: ${{ needs.calculate-artifact-name.outputs.artifact-name }}