Support OpenAPI reusable responses in global components object (handle $ref properly everywhere)

[pmcelhaney]

This should fix #838.

• remove commented out code
• rename ResponseTypeCoder to ResponsesTypeCoder so we can factor our a coder for an individual response
• Factored out ResponseTypeCoder so that $refs will be followed
• code generator now properly handles $ref in a response
• extract TypeCoder class
• move the decision on whether to write code directly or import from another script (because the requirement is a $ref) up to Coder / TypeCoder

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f9a78c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coveralls]

Pull Request Test Coverage Report for Build 8697996524

Details

• 101 of 103 (98.06%) changed or added relevant lines in 8 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.09%) to 86.607%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/typescript-generator/response-type-coder.js	11	13	84.62%

Files with Coverage Reduction	New Missed Lines	%
src/typescript-generator/response-type-coder.js	2	95.69%

Totals
Change from base Build 8679856385:	0.09%
Covered Lines:	2879
Relevant Lines:	3369

---

💛 - Coveralls

[dethell]

Suggest using an enum instead of hard coded strings:

Suggested change

	const xType = script.importSharedType("WideOperationArgument");
	const xType = script.importSharedType(SharedType.WideOperationArgument);

[pmcelhaney]

These strings appear as both a type name and a runtime value. I don't think there's a way to share across those two different contexts. Otherwise good idea.

[dethell]

Same as above. Likely these types won't ever change, but it seems more future-proof.