feat(cli): prompting the user to use info.title for their installed SDK

[erunion]

🚥 Resolves #676

🧰 Changes

This slightly changes the installation process to now prompt the user if they would like to install their SDK using the info.title value from the API definition they supplied:

Note that this work only applies if they supply a non-ReadMe API Registry value to npx api install:

npx api install --identifier buster demo.json # will continue to use "buster"
npx api install @developers/v2.0#17273l2glm9fq4l # will continue to use "developers"
npx api install demo.json # will prompt the user if they want to use `info.title`

[erunion]

We should never get to this else case because info.title is required in an OpenAPI definition but just in case we don't have it for whatever reason, we'll just fallback to asking them what they want -- though codegen will likely fail immediately after this because of their invalid spec.

[kanadgupta]

The changes look good but I was thinking we do this with a different prompt flow where we prompt the user for the identifier, but rather than having two questions to handle this, we have one question (i.e., 'What would you like to identify this API as?') with the initial value set to the slugified info.title field. This would be spiritually similar to how we have a sensible initial value when reducing a spec file in rdme:

https://github.com/readmeio/rdme/blob/b8046fb083815924c51e3dbf7c419ea0a8e7ae6c/src/cmds/openapi/reduce.ts#L168-L175

Let me know what you think! I like how it's fewer prompts/keypresses with my idea, but I do like the explicitness of your approach

[erunion]

Revised this a bit and now there's just a single identifier question with a new initial value based on info.title if it's present.