Cosmos: handle fake LeftJoins in query tree

[roji]

Our preprocessing (nav expansion) produces LeftJoin nodes for owned entity collection, such as in the following case:

public virtual Task Filter_owned_entity_chained_with_regular_entity_followed_by_projecting_owned_collection(bool async)
    => AssertQuery(
        async,
        ss => ss.Set<OwnedPerson>().Where(p => p.PersonAddress.Country.Planet.Id != 42).OrderBy(p => p.Id)
            .Select(p => new { p.Orders }),
        assertOrder: true,
        elementAsserter: (e, a) => AssertCollection(e.Orders, a.Orders));

Of course, in Cosmos (and in relational JSON), p.Orders doesn't represent a join at all; so we need to ignore it, reverse-engineering the original query so that this can be translated.

Long-term, we should get rid of these nodes altogether by removing nav expansion as a preprocessing step (#32957).

[roji]

These turned out to be non-fake LeftJoins, since a non-owned entity (Planet) is accessed in the query above. Will introduce a specialized translation failure message for this case, and scrub the tests hitting this (see #34066).

[ajcvickers]

@roji Should this be closed-fixed and in a release, or closed-no-further-action and then closed as not-planned?

[roji]

Thanks for going over these @ajcvickers. This ended up being an error message tweak and a test cleanup, am placing in the 9.0 milestone as closed-fixed.