[Chore] Fix DEFAULT_MAX_RETRIES value from 0 to 2

[prassanna-ravishankar]

CI was broken

[smoreinis]

Can we just fix the test expectation here? I'm not sure if there was a reason why we wanted to actually reduce the default number of max retries to 0 cc @jasonyang101

[prassanna-ravishankar]

Can we just fix the test expectation here? I'm not sure if there was a reason why we wanted to actually reduce the default number of max retries to 0 cc @jasonyang101

AFAIK the core issue is the default. I asked claude to do a bisect + analysis

1. Retry behavior should be > 0 by default: A default of 0 retries means no resilience to transient network issues, which is poor UX for an SDK.
2. Test expectations were more logical: The tests expecting 2 retries suggest this was the intended design.
3. Industry standards: Most HTTP clients default to 2-3 retries for better reliability.
4. The bisect revealed the issue: The assert self.client.max_retries == 2 assertions have been in the codebase for a long time, indicating this was always the intended behavior.

[smoreinis]

ok, I checked and it doesn't sound like anything's relying on this change having been made in https://github.com/scaleapi/agentex-python/pull/108/files so I'm ok with having it back at 2. thanks!