feat(deducer): slim down the python bundle, support cross-platfrom deployment

.changeset/odd-icons-speak.md

@@ -0,0 +1,9 @@
+---
+"@plutolang/pyright-deducer": patch
+---
+
+feat: using `pip install` to bundle dependencies instead of copying local packages
+
+When creating the Lambda deployment package, it's essential to bundle dependencies. Previously, we built the dependency graph for a single closure, identified the directories containing the dependent packages, and copied them into the deployment package. However, this approach struggles with cross-architecture deployment and may include unnecessary files.
+
+Now, we utilize `pip install` to install directly dependent packages for a closure. If the target runtime or architecture differs from the local environment, we employ Docker to handle dependency installation before packaging. While this method offers greater reliability, it's slower compared to the previous approach.

.changeset/tasty-suns-warn.md

@@ -0,0 +1,5 @@
+---
+"@plutolang/base": patch
+---
+
+fix(sdk): generating inconsistent resource id between python and typescript

components/deducers/python-pyright/package.json

@@ -22,13 +22,18 @@
   },
   "dependencies": {
     "@plutolang/base": "workspace:^",
+    "cross-spawn": "^7.0.3",
     "fs-extra": "^11.1.1",
-    "pyright-internal": "file:./libs/pyright-internal"
+    "glob": "^10.3.10",
+    "pyright-internal": "file:./libs/pyright-internal",
+    "shell-quote": "^1.8.1"
   },
   "devDependencies": {
+    "@types/cross-spawn": "^6.0.6",
     "@types/fs-extra": "^11.0.4",
     "@types/jest": "^29.5.12",
     "@types/node": "^20",
+    "@types/shell-quote": "^1.7.5",
     "jest": "^29.7.0",
     "jest-junit": "^16.0.0",
     "ts-jest": "^29.1.2",