Access is only checked against entity instead of the current language translation

Problem/Motivation

This change is based on an active core issue that addresses a similar problem with regular exposed filters (whose patch changes did not apply to facet exposed filters).

When using taxonomy terms with facets exposed filters in a view, access was not checked against translations. This meant that a term was still shown, even if that term was unpublished for the active language and, vice-versa, if a term was unpublished in the original language but published for the active language, it would not be shown.

I added a patch showcasing a possible solution (which was sufficient for my use case). This patch also hides terms without a translation for the current language to correspond with the regular exposed filter behavior after applying the core patch.

As an aside: I came across this Facets issue while checking the queue. The latest patch there removes the language manager that is used in this patch (I didn't want to take this into account for the patch and base myself on the current module version instead, but I feel like I should mention it).