Generate unique names for synthesized schemas like ContentType

[daviwil]

This change addresses an issue found by @ShivangiReja when using a newer version of the Form Recognizer spec. When the always-create-content-type-parameter option is used and image/bmp content type is added to only one of the 3 operations that accept image types, an additional SealedChoiceSchema with the name ContentType is created, causing the "checker" phase to fail with a duplicate schema name. This is also possible when synthesizing Accept headers.

The fix is to ensure uniqueness of these generated header names by adding logic to increment a numeric suffix that gets applied when more than one schema with a particular name is created.

[fearthecowboy]

lgtm

[azure-pipelines]

You may test this build by running autorest --reset and then either:

---

add --use: to the command line:

autorest --use:https://tinyurl.com/y5w8lhky ...

---

or use the following in your autorest configuration:

use-extension:
  "@autorest/modelerfour": "https://tinyurl.com/y5w8lhky" 

---

If this build is good for you, give this comment a thumbs up. (👍)

And you should run autorest --reset again once you're finished testing to remove it.

[ShivangiReja]

looks great @daviwil! I'm able to generate Form Recognizer using the newer version correctly with this change.

[daviwil]

Awesome, thanks @ShivangiReja!

[azure-pipelines]

You may test this build by running autorest --reset and then either:

---

add --use: to the command line:

autorest --use:https://tinyurl.com/y3jnnhul ...

---

or use the following in your autorest configuration:

use-extension:
  "@autorest/modelerfour": "https://tinyurl.com/y3jnnhul" 

---

If this build is good for you, give this comment a thumbs up. (👍)

And you should run autorest --reset again once you're finished testing to remove it.