[tune] Update Lightning examples to support PTL 1.5

[kaushikb11]

Why are these changes needed?

Related issue number

To helps resolve the issues users are facing with running Lightning examples with Ray Tune Lightning-AI/pytorch-lightning#10407

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

[awaelchli]

@kaushikb11 here is possibly another change we need to make:

ray/python/ray/tune/integration/pytorch_lightning.py

Line 177 in ac843a9

if trainer.running_sanity_check:

it was renamed to sanity_checking. Should I send a separate PR?

[amogkam]

@kaushikb11 can you also update the version specified here to 1.5.3- https://github.com/ray-project/ray/blob/master/python/requirements/ml/requirements_tune.txt#L32.

This will make sure that we run with the latest PTL version in our CI.

[bveeramani]

‼️ ACTION REQUIRED ‼️

We've switched our code formatter from YAPF to Black (see #21311).

To prevent issues with merging your code, here's what you'll need to do:

1. Install Black

pip install -I black==21.12b0

2. Format changed files with Black

curl -o format-changed.sh https://gist.githubusercontent.com/bveeramani/42ef0e9e387b755a8a735b084af976f2/raw/7631276790765d555c423b8db2b679fd957b984a/format-changed.sh
chmod +x ./format-changed.sh
./format-changed.sh
rm format-changed.sh

3. Commit your changes.

git add --all
git commit -m "Format Python code with Black"

4. Merge master into your branch.

git pull upstream master

5. Resolve merge conflicts (if necessary).

After running these steps, you'll have the updated format.sh.