Weekly Patch Release v1.3.3 [full merge, no squash]

[awaelchli]

What does this PR do?

Next patch release after #7589

Related to #7467

gh pr list -s merged -S 'merged:2021-05-19T16:30:00.000Z..2021-05-26T23:30:00.000Z' --json mergedAt,milestone,url,mergeCommit,title --jq 'sort_by(.mergedAt) | reverse | .[] | select((.milestone.title == "v1.3.x") or (.milestone.title == null)) | [.url, .mergeCommit.oid, .title] | join(" ")' --limit 100

ok #7692 8ba6304 Increment the total batch idx before the accumulation early exit
ok #7683 2c10ecc MAINTAINER has been deprecated
no #7676 ad168fc chlog for 1.3.2 + legacy test
ok #7677 8b01497 Fix global step update when the epoch is skipped
ok #7415 3f460b1 Move parameter validation specific to TPU Training plugins
ok #7674 a54bc5d Fix progress bar print error when called before training
ok #7566 0c958c5 Fix dataloaders are not reset when tuning the model
ok #7563 01109cd Fix/mismatched toggle optimizer
no #7639 03ea68f Removed hparams assignment example in doc
ok #7592 92cf396 Override broadcast_object_list for torch<1.8
ok #7608 ed27190 Clear predict_progress_bar in ProgressBar.getstate
no #7606 6e56f56 docker use $(nproc)
no #7598 922c0a6 Fix incorrect code-snippet in optimizers doc

Questions:

• Should Move parameter validation specific to TPU Training plugins #7415 be included since it is a follow up to a bugfix PR?

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[codecov]

Codecov Report

Merging #7712 (200b5b6) into release/1.3.x (6b81cd8) will decrease coverage by 5%.
The diff coverage is 90%.

@@              Coverage Diff               @@
##           release/1.3.x   #7712    +/-   ##
==============================================
- Coverage             92%     87%    -5%     
==============================================
  Files                200     200            
  Lines              13004   13013     +9     
==============================================
- Hits               11951   11371   -580     
- Misses              1053    1642   +589     

[tchaton]

LGTM !

[carmocca]

(not blocking) extra whitespace

Suggested change