Translation outdated field on views doesn't hide if the site is mono-lingual

Problem/Motivation

With a multi-site setup (but shared config) where at least 1 site is multilingual, if you add the language + if the translation is outdated to the /admin/content view, the language column gets hidden on the monolingual sites. This makes sense as they're all the same language and was done under #2473989: Lack of dynamic language field / filter makes shipping core views hard to be both compatible with mono and multilingual, however the "translation is outdated" column should also get hidden/removed.

Steps to reproduce

1. Create a monolingual site with content translation enabled
2. Add the language and "translation is outdated" fields to a view
3. Observe the language column is hidden/removed but the "translation is outdated" remains.

Proposed resolution

Hide the "translation is outdated" field too.

Remaining tasks

• Do we need to extend to the filter?
• Test coverage

User interface changes

By default none.

Introduced terminology

N/A

API changes

N/A

Data model changes

N/A

Release notes snippet

N/A