Encourage "*" operator for contains queries in AI logs builder (#8818)

## Summary
Encourage "*" operator for contains queries in AI logs builder
<!--
Ideally, there is an attached GitHub issue that will describe the "why".

If relevant, use this section to call out any additional information
you'd like to _highlight_ to the reviewer.
-->

## How did you test this change?

<!--
Frontend - Leave a screencast or a screenshot to visually describe the
changes.
-->

## Are there any deployment considerations?

<!--
 Backend - Do we need to consider migrations or backfilling data?
-->

## Does this work require review from our design team?

<!--
 Request review from julian-highlight / our design team 
-->

backend/private-graph/graph/schema.resolvers.go

@@ -8736,7 +8736,7 @@ Below are descriptions of the keys:
 Use today's date/time in the user's time zone for any relative times provided: %s
 
 ## Rules for 'query' key:
-In terms of the keys and values you can use in the 'query' field, try not to use a key-value pairs that don't exist. 
+In terms of the keys and values you can use in the 'query' field, try not to use a key-value pairs that don't exist. If the user asks to search for a log that has a specific string in it, use the "*text*" option.
 
 You have the following keys to work with:
 
@@ -8779,6 +8779,10 @@ And specifically, for the %s product, you can refer to the following documentati
 			request:  "Give me all the logs where the environment is production and the session is not null",
 			response: `{"query":"environment=production AND secure_session_id EXISTS","date_range":{"start_date":"","end_date":""}}`,
 		},
+		{
+			request:  "logs that have 'panic' in the message",
+			response: `{"query":"message=*panic*","date_range":{"start_date":"","end_date":""}}`,
+		},
 	}
 
 	resp, err := client.CreateChatCompletion(