Changed tune.report import for ray>=2

[drwillcharles]

Why are these changes needed?

When using ray>=2, there is an import error for tune.report.

AttributeError: module 'ray.tune' has no attribute 'report'

I used the Ray migration guide to update this and use the new report function if the ray version is not 1.x .

I see that in the FLAML codebase there are already a few workarounds like this so I think I can do something similar without needing a full migration to Ray 2.x

Related issue number

Related to #874 - although I still think a full migration to Ray>=2 is needed in the future.

Checks

• [ x] I've used pre-commit to lint the changes in this PR (note the same in integrated in our CI checks).
• [x ] I've included any doc changes needed for https://microsoft.github.io/FLAML/. See https://microsoft.github.io/FLAML/docs/Contribute#documentation to build and test documentation locally.
• [ x] I've added tests (if relevant) corresponding to the changes introduced in this PR.
• [x ] I've made sure all auto checks have passed.

[drwillcharles]

@microsoft-github-policy-service agree company="Evotec"