Extension has just one function, which is to quickly load attributes as opposed to loading them slowly. That is only a choice that the query builder has.
None other than s in SQL.
You're attempting to implement internal filtering
phrase that is incorrect.
I'm not sure whether filtering an inner collection can be accomplished with only one EF query, however you may check out a related question like How can I filter Entity Framework objects in nested collections?.