write a go solution for G1. Ruler (easy version)time limit per test1 secondmemory limit per test256 megabytesinputstandard inputoutputstandard outputThis is the easy version of the problem. The only difference between the two versions is that in this version, you can make at most mathbf10 queries.This is an interactive problem. If you are unsure how interactive problems work, then it is recommended to read the guide for participants.We have a secret ruler that is missing one number x (2<=x<=999). When you measure an object of length y, the ruler reports the following values:   If y<x, the ruler (correctly) measures the object as having length y.  If y>=qx, the ruler incorrectly measures the object as having length y+1.  The ruler above is missing the number 4, so it correctly measures the first segment as length 3 but incorrectly measures the second segment as length 6 even though it is actually 5. You need to find the value of x. To do that, you can make queries of the following form:  texttt?~a~b — in response, we will measure the side lengths of an axb rectangle with our ruler and multiply the results, reporting the measured area of the rectangle back to you. For example, if x=4 and you query a 3x5 rectangle, we will measure its side lengths as 3x6 and report 18 back to you. Find the value of x. You can ask at most mathbf10 queries.InputEach test contains multiple test cases. The first line of input contains a single integer t (1<=t<=1000) — the number of test cases.InteractionThere is no initial input for each test case. You should begin the interaction by asking a query.To make a query, output a single line of the form texttt?~a~b (1<=a,b<=1000). In response, you will be told the measured area of the rectangle, according to our secret ruler.When you are ready to print the answer, output a single line of the form texttt!~x (2<=x<=999). After that, proceed to process the next test case or terminate the program if it was the last test case. Printing the answer does not count as a query.The interactor is not adaptive, meaning that the answer is known before the participant asks the queries and doesn't depend on the queries asked by the participant.If your program makes more than 10 queries for one set of input data, makes an invalid query, or prints the wrong value of x, then the response to the query will be -1. After receiving such a response, your program should immediately terminate to receive the verdict Wrong Answer. Otherwise, you can get an arbitrary verdict because your solution will continue to read from a closed stream.After printing a query do not forget to output the end of line and flush the output. Otherwise, you may get Idleness limit exceeded verdict. To do this, use:   fflush(stdout) or cout.flush() in C++;  System.out.flush() in Java;  flush(output) in Pascal;  stdout.flush() in Python;  see the documentation for other languages. HacksTo make a hack, use the following format.The first line should contain a single integer t (1<=t<=1000) — the number of test cases.The only line of each test case should contain a single integer x (2<=x<=999) — the missing number on the ruler.ExampleInput2

18

25


9999Output? 3 5

? 4 4

! 4
? 99 100

! 100NoteIn the first test, the interaction proceeds as follows. SolutionJuryExplanationtexttt2There are 2 test cases.texttt?35texttt18Secretly, the jury picked x=4. The solution requests the 3x5 rectangle, and the jury responds with 3x6=18, as described in the statement.texttt?44texttt25The solution requests the 4x4 rectangle, which the jury measures as 5x5 and responds with 25.texttt!4The solution has somehow determined that x=4, and outputs it. Since the output is correct, the jury continues to the next test case.texttt?99100texttt1Secretly, the jury picked x=100. The solution requests the 99x100 rectangle, which the jury measures as 99x101 and responds with 9999.texttt!100The solution has somehow determined that x=100, and outputs it. Since the output is correct and there are no more test cases, the jury and the solution exit. Note that the line breaks in the example input and output are for the sake of clarity, and do not occur in the real interaction.. Output only the code with no comments, explanation, or additional text.