[Data] Add environment variable support for Ray Data execution callbacks.

[JDarDagran]

Why are these changes needed?

This change adds support for loading Ray Data execution callbacks from an environment variable (RAY_DATA_EXECUTION_CALLBACKS). Users can now specify a comma-separated list of callback class paths, which will be dynamically imported and added to the DataContext.
This allows for easy instrumentation and monitoring of Ray Data executions without modifying application code, which is useful for deb ugging and observability in production environments.

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