fix(type-safe-api): missing runtime modules in Lambda deployment (#815)

Fixes the issue where generated runtime modules were not packaged
in the Lambda deployment, causing ImportModuleError when executing
Python handlers.

The fix modifies the packaging task in GeneratedPythonHandlersBaseProject
to strip the '-e' flag from exported requirements.txt. This ensures runtime
modules are installed as regular packages instead of editable installations.

Changes:
- Update 'poetry export' command to pipe output through 'sed' and remove
  '-e' prefix.
- Update corresponding snapshot tests for new package task command.

Fixes #791

Co-authored-by: Adrian Dimech <51220968+agdimech@users.noreply.github.com>

packages/type-safe-api/src/project/codegen/handlers/generated-python-handlers-base-project.ts

@@ -132,7 +132,7 @@ export abstract class GeneratedPythonHandlersBaseProject extends PythonProject {
       `cp -r ${this.moduleName} dist/lambda/${this.moduleName}`
     );
     this.packageTask.exec(
-      "poetry export --without-hashes --format=requirements.txt > dist/lambda/requirements.txt"
+      "poetry export --without-hashes --format=requirements.txt | sed -E 's/^-e[[:space:]]+//' > dist/lambda/requirements.txt"
     );
     // Select the platform based on the specified architecture, defaulting to x86_64
     // See: https://docs.aws.amazon.com/lambda/latest/dg/python-package.html#python-package-native-libraries