CLOUDP-333877: create stub for atlas cli commands streams workspaces and streams workspaces create

[Waybo26]

Proposed changes

Layout framework for switching atlas cli command instances over to workspaces; starting with workspaces create.

Jira ticket: CLOUDP-333877

Checklist

• I have signed the MongoDB CLA
• I have added tests that prove my fix is effective or that my feature works
• I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
• I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
• I have updated test/README.md (if an e2e test has been added)
• I have run make fmt and formatted my code

[kpatel71716]

good work! some small things from a first pass

[github-actions]

Coverage Report 📉

Branch	Commit	Coverage
master	d165a3f	25.9%
CLOUDP-333877	790b073	%
	Difference	-25.9%

[coveralls]

coverage: 65.017% (-0.08%) from 65.098%
when pulling ea66a4b on CLOUDP-333877
into e84041f on master.

[kpatel71716]

LGTM! Can we add a update the PR title + edit the description to this PR to indicate that this is laying the groundwork for the command rename but is not adding the command for usage yet?

[fmenezes]

Unfortunately, this PR was merged without our team reviewing, code owners was not enforced (I've enabled it now).

I happen to notice there is no new API in this code, is the intention here to alias an existing command instead?

When are you introducing new e2e tests?

[Waybo26]

My apologies for not waiting for a review. I can revert the PR or address any issues in a follow-up ticket I'm working on to integrate atlas streams workspaces update into the same framework that this PR addresses.
The new e2e tests will be included when the api is updated to generate the new fields that will be called by the command atlas streams workspaces (the new fields being defaultTier and maxTierSize)

[kpatel71716]

I happen to notice there is no new API in this code, is the intention here to alias an existing command instead?

We are planning on renaming the command from instance to workspace but we went away from aliasing because we want to add functionality to only workspace so users switch to that command. For now we are just adding underlying logic because we don't want the new command to be available yet