Add nebari typer cli changes

[asmijafar20]

Reference Issues or PRs

What does this implement/fix?

Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Documentation

Access-centered content checklist

Text styling

• The content is written with plain language (where relevant).
• If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• All links describe where they link to (for example, check the Nebari website).
• This content adheres to the Nebari style guides.

Non-text content

• All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing GIFs or videos.
• If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

[netlify]

✅ Deploy Preview for nebari-docs ready!

Name	Link
🔨 Latest commit	53bfd11
🔍 Latest deploy log	https://app.netlify.com/sites/nebari-docs/deploys/63516cb0a50c0d0009f68c87
😎 Deploy Preview	https://deploy-preview-150--nebari-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[trallard]

Thanks for opening this PR @asmijafar20 it looks in pretty good shape. I added some comments and suggestions here and there.

I assume the GCP, Azure and DO docs will be updated as well.

[asmijafar20]

I added the suggested changes but didn't change the screenshots specifically for each cloud provider. I will do that once we have the final structure of the CLI.

[iameskild]

Thanks again @asmijafar20 for all your work on the CLI and docs :)

@pavithraes I believe this is ready to merge! Thanks for the thorough review as always :)

[pavithraes]

Thank you for the updates! I've added back some nebari mentions that probably got overridden when merging main. We should be good to merge after this! ✨

[iameskild]

@pavithraes sorry for the untidy merge conflict clean up 😅

I think this is ready to be merged now 🙌

[pavithraes]

Thank you! I agree that we can merge. :)

I see a couple of things to update at a later date, and I've noted them in #188:

Link to the advanced configurations page about nebari-config.yaml in the cloud provider specific how-tos (2nd point under Nebari initialize). It currently links to qhub.dev. And, update in the output: QHUB_DEFAULT_PASSWORD to Nebari if/when that change is made.