Allow specification of a custom interface name

[queengooborg]

This PR adds a new tsName schema property that allows a developer to overwrite the default generated name. This is super helpful in cases where two interfaces/types are generated with the same name (and one has a numerical increment), or where the developer may wish to ensure backwards compatibility of their TypeScript definitions.

Before:

/**
 * This interface was referenced by `Browsers`'s JSON-Schema
 * via the `definition` "browsers".
 */
export type Browsers1 = Record<string, BrowserStatement>;

export interface Browsers {
  browsers?: Browsers1;
}

After:

/**
 * This interface was referenced by `Browsers`'s JSON-Schema
 * via the `definition` "browsers".
 */
export type Browsers = Record<string, BrowserStatement>;

export interface BrowsersData {
  browsers?: Browsers;
}

This is related to #181 (and potentially resolves it?). Unlike #215, however, this PR aims to grant the developer more finite control over the names.

[bcherny]

Seems reasonable! A few minor suggestions before we merge this.

[bcherny]

Please also add a test case for when title is defined, and another for when description is defined. Thanks!

[queengooborg]

I didn't realize that title was an actual schema property! In that case, the title property solves the problem for our use case, but I'll still update the tests and see this PR through to the end!

[bcherny]

If title works for your use case, we can also pause the work on this PR. No need to add more options unless there’s strong demand for them.

[bcherny]

Can you just add a single inline boolean property? This test case is about naming, so we can simplify it to remove the definitions.

[bcherny]

Closing out stale PRs. Feel free to rebase and re-open if you'd like to revisit this PR.