Disable /search dry parameter in non-debug builds & harmonize endpoint results

[leovalais]

The dry parameter is useful for debugging the query being generated by the search expression. It's not necessary in production. Moreover we spotted during the axum migration that the /search endpoint sometimes returns json (search results) or text (dry). This PR harmonizes that.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 37.50000% with 5 lines in your changes missing coverage. Please review.

Project coverage is 36.87%. Comparing base (5038159) to head (84d3107).
Report is 2 commits behind head on dev.

Files with missing lines	Patch %	Lines
editoast/src/views/search.rs	0.00%	5 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff              @@
##                dev    #8673      +/-   ##
============================================
- Coverage     36.88%   36.87%   -0.02%     
  Complexity     2213     2213              
============================================
  Files          1253     1253              
  Lines        113838   113832       -6     
  Branches       3185     3185              
============================================
- Hits          41991    41974      -17     
- Misses        69955    69966      +11     
  Partials       1892     1892              

Flag	Coverage Δ
core	74.75% <ø> (ø)
editoast	71.89% <0.00%> (-0.05%)	⬇️
front	14.94% <100.00%> (+<0.01%)	⬆️
gateway	2.20% <ø> (ø)
osrdyne	2.71% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	86.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[flomonster]

Sounds good to me, but I'm not sure I understand the purpose of PR...
Can you add some context to the PR description?

[leovalais]

Sounds good to me, but I'm not sure I understand the purpose of PR... Can you add some context to the PR description?

Good point, sorry. Updated. While doing that I recalled we needed to change the response of the endpoint. This PR now also includes that.

[flomonster]

LGTM