chore: pin Bamboo and Lotus Next actor baseline

[bigduu]

Summary

• Pin Bamboo at the merged dev revision e7e9c380a470d4079acabadae8c378b6e232c550 from Bamboo #1476.
• Pin Lotus Next at the merged main revision e2acf6c4c47673c34fec7686e155820df776a25e from Lotus Next #214.
• Deliver the two accepted source revisions together through one Zenith pointer update. No unrelated root files change.

Submodule Updates

• bamboo: advance from 350b55e2bee8f435b614bd7114e11598436ba726 to e7e9c380a470d4079acabadae8c378b6e232c550 so Zenith uses the merged durable actor tree, broker receipt recovery, and direct Child steering baseline.
• lotus-next: advance from 96a56afec49f5e60b021460a35d0422df231ae65 to e2acf6c4c47673c34fec7686e155820df776a25e so the frontend uses the merged actor tree cursor and snapshot recovery behavior.

Test plan

• git diff --cached --check passed before commit.
• Verified both exact 160000 gitlink revisions against the merged source PRs and live destination branches.
• Bamboo #1476 required Test passed; its cumulative local regression and targeted reruns are documented in that PR. Lotus Next chore: adopt Lotus Next live reading fix #214 passed npm run verify and browser acceptance before merge.

Refs bigduu/Bamboo-agent#791.