Code generation produces invalid code when a query parameter is named "query"

A query parameter named query results in variable shadowing that prevents the generated code from compiling. I would expect progenitor to detect this case and rename the generated query variable on line 7 to avoid the name collision.

See minimal example below:

    ///Sends a `GET` request to `/v0/leaderboards/ranked_1v1`
    pub async fn get_leaderboard<'a>(
        &'a self,
        query: Option<&'a str>,
    ) -> Result<ResponseValue<types::LeaderboardResponse>, Error<types::ErrorResponse>> {
        let url = format!("{}/v0/leaderboards/ranked_1v1", self.baseurl,);
        let mut query = Vec::with_capacity(1usize);

        if let Some(v) = &query {
            query.push(("query", v.to_string()));
        }

        let request = self
            .client
            .get(url)
            .header(
                reqwest::header::ACCEPT,
                reqwest::header::HeaderValue::from_static("application/json"),
            )
            .query(&query)
            .build()?;
        let result = self.client.execute(request).await;
        let response = result?;
        match response.status().as_u16() {
            200u16 => ResponseValue::from_response(response).await,
            500u16 => Err(Error::ErrorResponse(
                ResponseValue::from_response(response).await?,
            )),
            _ => Err(Error::UnexpectedResponse(response)),
        }
    }

Start with the minimal Rust example in the issue and the generator path that emits its query handling; reproduce the problem by compiling the generated function. Done when a query parameter named query no longer shadows the generated query collection and the generated Rust compiles.