What is the bug or the crash?
using a project in EPSG:2154, with a wcs layer in EPSG:2154, the 'spatial filter' section of the WCS add layer dialog uses WGS84 coordinates by default. Thus, the server returns no data, since the requested bbox doesnt match at all the layer extent.
Steps to reproduce the issue

which results in a query that doesn't make sense since CRS/RESPONSE_CRS is set to the requested projection, but the bbox is WGS84 (server is mapserver 8):
/expe_wcs?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&FORMAT=GTiff&COVERAGE=ortho&BBOX=3.22886608100000005,46.56819605100000103,3.23332050299999985,46.57000589599999785&CRS=EPSG:2154&RESPONSE_CRS=EPSG:2154&WIDTH=6&HEIGHT=3
clicking 'draw on map' or 'map extent' ('etendue du canevas de carte') changes the coordinates, but they're also in WGS84 projection.
manually entering EPSG:2154 coordinates/bbox works.
Versions
3.26.3
Supported QGIS version
New profile
Additional context
feature added in #45655 for #45407
What is the bug or the crash?
using a project in EPSG:2154, with a wcs layer in EPSG:2154, the 'spatial filter' section of the WCS add layer dialog uses WGS84 coordinates by default. Thus, the server returns no data, since the requested bbox doesnt match at all the layer extent.
Steps to reproduce the issue
which results in a query that doesn't make sense since CRS/RESPONSE_CRS is set to the requested projection, but the bbox is WGS84 (server is mapserver 8):
clicking 'draw on map' or 'map extent' ('etendue du canevas de carte') changes the coordinates, but they're also in WGS84 projection.
manually entering EPSG:2154 coordinates/bbox works.
Versions
3.26.3
Supported QGIS version
New profile
Additional context
feature added in #45655 for #45407