[Logs] Add runtime env started logs to job driver

[GeneDer]

Why are these changes needed?

Added runtime env started logs to job driver

Related issue number

Closes https://github.com/anyscale/product/issues/27790

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• 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 added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• 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 :(

[GeneDer]

Manually tested by submitting a job with runtime env to install a different version of pandas. Confirmed the timestamp of the runtime env start/ finished messages in the job driver log is right before/ after the runtime env start/ finished in the runtime env agent and setup logs

[alanwguo]

Hm, I'm a bit concerned about multiple processes writing to the same file. Will that work?

I see this SO thread that warns against it: https://stackoverflow.com/questions/15096090/python-separate-processes-logging-to-same-file

[GeneDer]

Hm, I'm a bit concerned about multiple processes writing to the same file. Will that work?

I see this SO thread that warns against it: https://stackoverflow.com/questions/15096090/python-separate-processes-logging-to-same-file

I see, thanks Alan! Let me try to work around it.

[alanwguo]

let's do.

"Runtime env is setting up."

I think by saying "is starting up", people may expect to see a "is completed" log message afterwards