[workflow]align the behavior of workflow's max_retires with remote function's max_retries

[lchu-ibm]

Why are these changes needed?

To address the issue #22824

Basically the current behavior of max_retries in workflow is different from the one in remote functions in the following ways:

1. workflow's max_retries is not the number of retries, but the number of total tries.
2. workflow's max_retries does not allow "-1" (infinite retries) while remote function's max_retries does.

This PR altered the behavior of max_retries in workflow to be consistent with the max_retries in remote functions:

1. make max_retries to be truly max retries (i.e. total tries = original try + max retries)

• implementation
• update logging
• update tests

2. make max_retries accept infinite tries (i.e. max_retries=-1)

Related issue number

#22824

Checks

• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[fishbone]

Overall LGTM. Some comments there.

[fishbone]

LG!