[csharp] Address MaxTimeout obsolete build warning

[alec-petersen]

@wing328 , this adds that option to enable use of MaxTimeout over Timeout, but it defaults to the non-obsolete option by default. Fix #19525.

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh ./bin/configs/*.yaml
  ./bin/utils/export_docs_generators.sh
  

  (For Windows users, please run the script in Git BASH)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[alec-petersen]

Good news @wing328! We can actually simplify down and lose the fallback config option. RestSharp already disregards MaxTimeout and uses the Timeout value, so setting Timeout will have the desired effect of using MaxTimeout.

[Obsolete("Use Timeout instead.")]
public int MaxTimeout {
    get => (int) (Timeout?.TotalMilliseconds ?? 0);
    set => Timeout = TimeSpan.FromMilliseconds(value);
}

[wing328]

tests passed via https://ci.appveyor.com/project/WilliamCheng/openapi-generator/builds/50804786

[wing328]

if users call the getter of Timeout in their code, they will need to update their code accordingly updating the C# client to a newer version including this change, right?

[alec-petersen]

Correct, if they use the 7.10.0 version of the generator to generate their client, they will need to update usages of Timeout.

[wing328]

Added an option useIntForTimeout for fallback via #20069, e.g. --addititional-properties useIntForTimeout=true in CLI