Do we know why this has been added in the first place?

Also, if we decide to remove it, we should remove it from the editor as well. Also, this is the only place where this class is used for Core blocks which means we need to remove the styles defined in common.scss for it as well.

Do we know why this has been added in the first place?

When looking at the PR in which this block has been introduced (#7949) I can't find a context about why this class was added in the first place.
I assume it's because they want to hide it (?) but still making it available in the screen reader tree.

Pinging @talldan @mcsf for more details.

The original PR matched the widget I believe

Also, if we decide to remove it, we should remove it from the editor as well.

It isn't what happens when I remove the class in /block-library/src/archives/index.php? It is removed in the editor and in the frontend.

The original PR matched the widget I believe

So it may be to avoid duplicate with the widget title 🤔

Also, this is the only place where this class is used for Core blocks which means we need to remove the styles defined in common.scss for it as well.

It is also used for the Core Search block

The original PR matched the widget I believe

It's been a long time, but I assume it was following prior art. I don't know how relevant that label still is.

@joedolson , do you think there's an accessibility context for this screen-reader-text class? Thanks :)

I also don't recall. It was one of the first PRs I contributed, but I mostly took over from a contributor that wasn't able to finish it.