BUG: Fix Specify Lines value in search query input on /temp route

[SiriChandanaGarimella]

Describe the bug Currently, the UI improvement is in progress, and on providing the Specify Lines value through the UI in /temp route, the system incorrectly interprets the value as [object Object] instead of the provided value. The system should display the chosen value of the dropdown followed by the specified line value if applicable.

To Reproduce Steps to reproduce the behavior:

1. Run the application and navigate to https://localhost:3000/temp
2. Choose the ORCA log file as the input and upload it.
3. Provide the following search inputs:
   • Search term (e.g., "CARTESIAN COORDINATES (A.U.)") and click on 'Enter'
   • Lines specified (e.g., FIRST 5)
   • Number of sections (e.g., 1, 2)
4. Click on F12 and open the developer tools
5. Navigate to the Network tab in the developer tools
6. Click on Download Output in the UI
7. In the Network tab, click on find-sections and navigate to the Payload tab. Check the specify_lines value in the Request Payload.
8. Open a new browser tab, navigate to https://localhost:3000/, and repeat the above steps from 2 to 7 with the same inputs.
9. Observe the difference in the specify_lines parameter value.

Expected behavior On /temp, the system should display "FIRST 5" instead of [object Object] if "First" is selected in the dropdown and the "lines specified" value is 5, and if "Whole" is selected in the dropdown, then "WHOLE" should be displayed in the specify_lines.

Screenshots https://localhost:3000/temp output:

https://localhost:3000/ output:

Additional context Make use of specifyLines[0].showInput, specifyLines[0].lineNumber, specifyLines[0].value in the DraftOrcaDashboard.js file to get the required values.