fix: add Deeploy lifecycle delete metadata

[cristibleotiu]

Summary

• advance Deeploy lifecycle generation in create/update/scale pipeline specs
• send structured Deeploy delete payloads using the discovered deployment generation
• carry pipeline Deeploy specs through discovery and extend delete command tests
• extend the local two-node Deeploy testbed with old-delete-after-newer-update validation and a local-core compose overlay

Why

Sender-side delete dedupe from DEEPLOY-0002 does not prevent a delayed older delete from stopping a newer updated app. This branch adds the Deeploy sender metadata needed by the receiver ordering guard.

Dependency

Depends on Ratio1/naeural_core#206. Do not deploy this branch without core support for structured DELETE_CONFIG payloads; old core reproduces TypeError: unhashable type: 'dict' when receiving dict delete content.

Validation

• PYTHONPATH=/mnt/c/workspaces/r1_wrapper/worktrees/deeploy-0003/naeural_core:/mnt/c/repos/naeural_client /home/bleot/venvs/umbrella313/bin/python -m unittest discover -s extensions/business/deeploy/tests -p 'test_*.py' -> 65 tests passed
• PYTHONPATH=/mnt/c/workspaces/r1_wrapper/worktrees/deeploy-0003/naeural_core:/mnt/c/repos/naeural_client /home/bleot/venvs/umbrella313/bin/python -m py_compile extensions/business/deeploy/deeploy_const.py extensions/business/deeploy/deeploy_mixin.py extensions/business/deeploy/tests/test_delete_pipeline_commands.py extensions/business/deeploy/tests/test_create_requests.py docker-compose/deeploy-testbed/validate_delete_workflow.py
• DEEPLOY_TESTBED_CORE_PATH=/mnt/c/workspaces/r1_wrapper/worktrees/deeploy-0003/naeural_core/naeural_core docker compose -f docker-compose/deeploy-testbed.yaml -f docker-compose/deeploy-testbed.local-core.yaml config --quiet
• Two-node Docker testbed: create generation 1, update generation 2, stale structured delete received but stream remains, current structured delete removes once per node, result ok
• git diff --check

Known Blocker

python -m unittest extensions.business.deeploy.test_deeploy is still blocked by the existing circular import around _UtilsBaseMixin; focused Deeploy tests pass.