fix(quick-add): scale automation timeouts

[milldr]

Summary

• scale quick-add automation timeouts with setup, macro count, and date navigation
• give automatic login enough time to complete on slow Cronometer sessions
• extend the remote browser lifetime to cover the longest supported quick-add flow
• add regression coverage for single- and multi-macro timeout budgets

Why

Cronometer logs each quick-add macro as a separate food-dialog operation. The previous shared 60-second deadline could save an early macro and abort later ones, leaving a partial diary entry that was unsafe to retry. Slow login sessions could hit the same fixed deadline before the write began.

Verification

• npm test — 229 tests passed
• npm run build
• npm run lint
• npm run format:check
• git diff --check

The patched local build was also exercised against a fat-only correction. It reached the login flow but Cronometer did not complete login before the expanded deadline; a read-only export confirmed no additional diary entry was created.

Want tembo to make any changes? Add a comment with @tembo and i'll get back to work!