Fix Staking with latest breaking changes!

[TarikGul]

closes: #10396
closes: #10482

With the most recent breaking changes in the api polkadot-js/api#5860 polkadot-js/api#5862 due to changes in pallet-staking, this PR hopes to fix a lot of those issues.

Just to preface, it is very possible that this PR does not fix every issue that might be present but it is a step in the right direction. What I mean by this is there is a lot changes and logic that were covered in the above PR's and it is difficult to track every single one down in the UI, and how that data might be nested to x amount of Components.

I also updated all the following deps:

@polkadot/api -> 11.0.1
@polkadot/extension -> 0.47.2
@polkadot/phishing -> 0.22.6
@polkadot/tools -> 0.56.8

Disclaimer!! This does not touch the page-staking2 components (As noted by Jaco it seems to have been a staking test app). When the time comes if needed I can update that as well.

[TarikGul]

Currently getting the error:

useCall.ts:43 Error: useCall(...):: -32006: Too many subscriptions on the connection: Exceeded max limit of 1024:: RpcError: -32006: Too many subscriptions on the connection: Exceeded max limit of 1024

I would assume it's from the following: https://github.com/polkadot-js/api/blob/master/packages/api-derive/src/staking/query.ts#L103-L126

[TarikGul]

By removing withClaimedRewardsEras it ended up working as is. Not sure how it effects claimedRewards yet though. I am also willing to just merge this in and fix that regression seperately.

[polkadot-js-bot]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.