Description

I messed up the release 26.4 when I picked up the 26.4 release a few days ago. Here is what happened:

The release branch is already merged into trunk: #24911. But I did not see that PR, and created another one: #24915. What's worse is that I merged the trunk branch into the release branch to solve merge conflicts. That means we have commits that are not intended to be released in the release branch. Also, the Localizable.strings files used by the translation process are changed after that merge.

Here is the commit that merged the trunk branch into the release branch: 74afbd0. From the commit, you can see the trunk commit was 808aafc.

Using this command, we can see the merged changes are 808aafc e5076c9.

$ git log `git merge-base 808aafcbc769dc44cccb183939ac229c56e1198d 61ef3bd20b0ee283103121a010bd84fbdb8865d9`..808aafcbc769dc44cccb183939ac229c56e1198d

808aafcbc7 Remove .newPublishingSheet FF (#24912)
e5076c9085 Remove .newsletterSubscribers FF (#24913)
18688610ff Merge release/26.4 into trunk (#24911)

This PR reverts those two commits in the release branch.

I'll remember to remove these two revert commits when merging the release branch into trunk. Update: commits were removed in #24933

Testing instructions