[REQ] `rust-axum` response naming scheme is bad

Is your feature request related to a problem? Please describe.

Generated response naming schemes for rust-axum is really bad:

pub enum DeleteOrderResponse {
    /// Invalid ID supplied
    Status400_InvalidIDSupplied,
    /// Order not found
    Status404_OrderNotFound,
}

This breaks Rust's naming conventions (PascalCase) and will trigger an endless amount of Clippy warnings (that I don't want to just ignore).

Describe the solution you'd like

I think a better naming scheme would be:

pub enum DeleteOrderResponse {
    /// Invalid ID supplied
    Status400InvalidIDSupplied,
    /// Order not found
    Status404OrderNotFound,
}

Or more true to Rust's conventions:

pub enum DeleteOrderResponse {
    /// Invalid ID supplied
    InvalidIDSupplied,
    /// Order not found
    OrderNotFound,
}

This can potentially generate duplicate names, but the compiler can catch the error just fine so it's not a real issue.

Describe alternatives you've considered

I tried to change the naming scheme in the configuration, but couldn't figure out how.

Start by locating the rust-axum generator code responsible for naming generated response enum variants, then inspect any related tests or snapshots. Compare the current underscore-separated names with the two proposed Rust-style alternatives and determine which behavior the project should standardize. Done means generated responses use the selected naming scheme without Clippy naming warnings, with tests covering the example cases.