[BUG] [Rust Server] yaml headers parameter in responses not match with required flag.

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator (example)?
• What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?
• [Optional] Bounty to sponsor the fix (example)

Description

[BUG] [Rust Server] yaml headers parameter in responses not match with required flag.

openapi-generator version

5.0.x

OpenAPI declaration file content or url

/repos/{repoId}:
parameters:
- in: path
name: repoId
schema:
type: string
required: true
get:
tags: [Repo, Info]
operationId: GetRepoInfo
responses:
"200":
description: OK

•      headers:
  

•        X-Cursor:
  

•          schema:
  

•            type: string
      content:
        application/json:
          schema:
            $ref: "#/components/schemas/StringObject"
  

Generated Rust Server code as following:

pub enum GetRepoInfoResponse {
/// OK
OK

• (String)

• {

•    body: String,
  

•    x_cursor: String
  

• }
  }
  //x_cursor is not optional.

Command line used for generation

bin/rust-server-petstore.sh

Steps to reproduce

bin/rust-server-petstore.sh

Related issues/PRs

NA

Suggest a fix

Generate x_cursor as Option<>.

Start with bin/rust-server-petstore.sh and the OpenAPI response-header example, then trace how the Rust server generator represents the X-Cursor header. Compare the generated GetRepoInfoResponse with the header's required setting; done means an optional header is generated as Option<> and the reproduction script produces the corrected output.