`AbstractXContentFilteringTestCase#testDotsAndDoubleWildcardInExcludedFieldName` is marked as `AwaitsFix`, linking #80160, but this issue is closed. We should either remove the AwaitsFix marker, open a new issue to track the bug, or remove the test if it is invalid.
libs/x-content/src/test/java/org/elasticsearch/xcontent/support/filtering/AbstractXContentFilteringTestCase.java
throws IOException {
        assertFilterResult(expected.apply(createBuilder()), filter(sample, includes, excludes, matchFieldNamesWithDots));
    }
    protected abstract void assertFilterResult(XContentBuilder expected, XContentBuilder actual);
    protected abstract XContentType getXContentType();
    @Override
    protected boolean removesEmptyArrays() {
        return true;
    }
    private XContentBuilder createBuilder() throws IOException {
        return XContentBuilder.builder(getXContentType().xContent());
    }
    private XContentBuilder filter(Builder sample, Set<String> includes, Set<String> excludes, boolean matchFieldNamesWithDots)
        throws IOException {
        if (matchFieldNamesWithDots == false && randomBoolean()) {
            return filterOnBuilder(sample, includes, excludes);
        }
        FilterPath[] excludesFilter = FilterPath.compile(excludes);
        if (excludesFilter != null && Arrays.stream(excludesFilter).anyMatch(FilterPath::hasDoubleWildcard)) {
            /*
             * If there are any double wildcard filters the parser based
             * filtering produced weird invalid json. Just field names
             * and no objects?! Weird. Anyway, we can't use it.
             */
            assertFalse("can't filter on builder with dotted wildcards in exclude", matchFieldNamesWithDots);
            return filterOnBuilder(sample, includes, excludes);
        }
        return filterOnParser(sample, includes, excludes, matchFieldNamesWithDots);
    }
    private XContentBuilder filterOnBuilder(Builder sample, Set<String> includes, Set<String> excludes) throws IOException {