docs: add local (non-pip) modules example for SLS-360

[deanq]

Summary

Adds 01_getting_started/05_local_modules/ — a CPU example that factors a Flash endpoint across local (non-pip) Python files: a sibling module (text_utils.py) and a package (greetings/, whose __init__ re-exports from a submodule). This is the capability delivered by SLS-360.

Depends on the SDK/worker change:

• SDK: feat: bundle local (non-pip) modules for serverless endpoints flash#352
• Worker: feat: import shipped local modules before executing user code runpod-workers/flash#100

What it demonstrates

• Importing a local sibling module and a local package (with __init__ + submodule) from an endpoint.
• In-function imports — required on the live path (only the function source + its local-module closure ship to the worker) and unchanged for flash deploy.

Verification (see the example README for commands)

• Build path (local): flash build bundles the sibling + package; a module dropped by the ignore filter (e.g. test_*.py) is force-included when an endpoint imports it; an unresolved endpoint import fails the build loudly.
• Deploy path (real endpoint): verified end-to-end — deployed to a real CPU endpoint, the worker imported the local modules and returned {"greeting": "HOLA, ADA!"}, then torn down.
• Live path (flash dev): works once the worker image from feat: import shipped local modules before executing user code runpod-workers/flash#100 is published (stock workers don't yet materialize inline modules); testable now via a locally-built worker image.

Notes

• .flash/ build artifacts are gitignored.
• Endpoint uses typed params (name, lang) so the queue handler's greet(**job_input) call binds {"input": {"name": ..., "lang": ...}} correctly.

[capy-ai]

Capy auto-review is paused for this organization because the usage-cycle auto-review limit has been reached. Increase the limit or turn it off in billing settings to resume automatic reviews.