Remove default fallback in tonic::service::Routes;

[nduchenk]

Feature Request

Motivation

Sorry for raising this issue if I missed some info.
Can't use tonic Routes with axum router with its own fallback:
Cannot merge two Routers that both have a fallback. This is an axum error, but it appears that tonic Routes by default set fallback:

tonic/tonic/src/service/router.rs

Line 54 in 6d93c1d

router: axum::Router::new().fallback(unimplemented),

As a result in example like this you receive an error, then have to find where another fallback comes from so to overwrite it or if you don'y use any fallback you get one from tonic Routes for all of your handlers which might be unexpected or not very obvious.

async fn hello() -> impl axum::response::IntoResponse {
    "Hello, World!"
}

async fn im_a_teapot() -> impl axum::response::IntoResponse {
    (StatusCode::IM_A_TEAPOT, "IM_A_TEAPOT")
}

#[tokio::main]
async fn main() {
    let app = Router::new().route("/hello", get(hello));
    // .fallback(im_a_teapot); <--- if added will fail in runtime.

    let tonic_routes = Routes::new(EchoServer::new(MyEcho)).into_axum_router();
    let app = app.merge(tonic_routes);

    let listener = tokio::net::TcpListener::bind("127.0.0.1:8000")
        .await
        .unwrap();

    axum::serve(listener, app).await.unwrap();
}

Proposal

Remove default fallback from:

tonic/tonic/src/service/router.rs

Line 54 in 6d93c1d

router: axum::Router::new().fallback(unimplemented),

Alternatives