Cut release-0.11.0 candidate branch again

Since we cut release-0.11.0 candidate branch, we have introduced several bug-fixes (list of new commits [here](https://github.com/apache/pinot/compare/release-0.11.0...master)), and several of them are critical because we recently upgraded several dependencies. I checked all the new commits, none of them can break the existing use cases.

Since we haven't released `0.11.0`, I would propose to re-cut the release candidate branch to include these new commits.

cc @atris @siddharthteotia @mayankshriv @walterddr for opinions

Start by reviewing the release-0.11.0...master comparison linked in the issue and verify which bug-fix commits should be included. Check the project's release-branch process before acting; done means a new release-0.11.0 candidate branch contains the approved commits without breaking existing use cases.

Written by the indexing model from the issue text.