BUG: KeyError when a series popped from data frame with bool indexer

- [x] closes #42530
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [x] whatsnew entry

thanks @debnathshoham  @meeseeksdev backport 1.3.x Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
$ git checkout 1.3.x
$ git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
$ git cherry-pick -m1 28ea152c33fc88c6c0607d2ae02e96933a9b26dd
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
$ git commit -am 'Backport PR #42644: BUG: KeyError when a series popped from data frame with bool indexer'
```

4. Push to a named branch :

```
git push YOURFORK 1.3.x:auto-backport-of-pr-42644-on-1.3.x
```

5. Create a PR against branch 1.3.x, I would have named this PR:

> "Backport PR #42644 on branch 1.3.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                 @simonjayhawkins you are right, the release note is in the wrong place. just doing the backport now with the release note in 1.3.2. and then a separate PR to move the release note (which won't need a backport, unless we get conflicts in the meantime and I need to resync)