Convert export events to proto and flush from background thread

[nikitavemuri]

Why are these changes needed?

Updated export event write logic to improve performance:

• Actors: Convert actor table data to export event proto and write log and flush on separate thread.
• Tasks: Task export event proto is already being created on a separate thread in the task_event_buffer, so only move log and flush to RayEventLog background thread.
• Nodes and Driver Jobs: No changes here because we aren't too concerned about performance due to relatively lower volume of events.

Improvement in actor creation throughput observed in release tests with FF on: https://buildkite.com/ray-project/release/builds/22806. * Note: This doesn't address regression in actor calls and task latency, that is still being investigated

Related issue number

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 :(