Filter parameters _and and _or are not considered valid by auth checks when an operation is authenticated

[eddiesholl]

Describe the bug
If a query is authenticated, it is not possible to provide a filter using _and or _or. It fails with an error like:

`Could not determine field metadata for filter key: '_and on AccordionItem entity'","stack":"Error: Could not determine field metadata for filter key: '_and on AccordionItem entity'\n at recurseThroughArg (.../@exogee/graphweaver-auth/lib/decorators/hooks/acl.js:169:15)

The auth module is trying to traverse the filter, but doesn't know what to do with _and and _or operations.

graphweaver/src/packages/auth/src/decorators/hooks/acl.ts

Line 248 in b61b1f3

if (!fieldMetadata) {

This is where the metadata is being processed, I think this piece is fine

graphweaver/src/packages/core/src/metadata.ts

Line 636 in b61b1f3

public fieldMetadataForFilterKey(

To Reproduce
Steps to reproduce the behavior:

1. Set up an entity with ACLs
2. Create a query that supplies a filter, and it uses _and or _or
3. Execute the query
4. See the error that occurs at runtime

An example query is

	query accordionItems($location: AccordionLocation!, $council: String) {
		accordionItems(
			filter: {
				_and: [{ location: $location }, { _or: [{ council: $council }, { council_null: true }] }]
			}
			pagination: { orderBy: { itemOrder: ASC } }
		) {
			id
			location
			title
			content
			itemOrder
			isExpanded
		}
	}

Expected behavior
The query should be allowed to proceed by auth

Actual behavior
What actually happened.

Screenshots or Screencasts
If applicable, add screenshots or screencasts to help explain the issue.

Desktop (please complete the following information):

• OS and version: [e.g. MacOS 13.3.1, Windows 11 v22H2]

Additional context
Add any other context about the problem here.