feat: Add stream_workspace resource + ds to replace stream_instance

[kpatel71716]

Description

CLOUDP-335390 As part of the effort to rename Atlas Stream Processing Instances to Workspaces, we are adding a new stream_workspace resource/datasource to replace stream_instance

Link to any related issue(s):

Type of change:

• Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
• New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
• Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contributing guides
• I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code
• If changes include deprecations or removals I have added appropriate changelog entries.
• If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

[kpatel71716]

Please review by individual commit to filter out all the docs updates. My thought was that we can take an initial approach to convert the stream workspace model to the stream instance model and back to reduce code duplication. Happy to take a different approach if the team does not feel comfortable with this approach

As a follow-up to this PR we can consider refactoring this approach, but for now I felt it provides functionality without making the PR too complex. I mostly copied over a lot of the stream instance code to achieve the addition of the new resource and datasource

[github-actions]

APIx bot: a message has been sent to Docs Slack channel

[xargom]

lgtm

[kpatel71716]

Added logical commits to refactor the docs, simplify var naming that was copy/pasted over + remove copied unused methods, and refactored the workspace/instance struct mapping logic for a better intermediate solution as we transition

[EspenAlbert]

Filenames should not have the resource name. New convention similar to streamprocessor instead (remove stream_workspace from the name)

[EspenAlbert]

I would try to re-use also the API calls, then we can just run instanceModel := streaminstance.Create(streamInstance, diags *diag.Diagnostics) and it returns the converted streaminstance.TFModel.
Then you can simply check diags.HasError() after call and only do the workspaceModel = FromInstanceModel(instanceModel)

[kpatel71716]

Would this imply that we need to convert the streamWorkspace object to a streamInstance to call this? I am thinking we could create a reusable method for newStreamWorkspaceCreateReq since we don't need to pass in the entire plan and can pass individual fields instead

I am fine keeping the stream instance and stream workspace separate at that level for now. As one day we might add features to stream workspace that we don't support for stream instance. So converting to streamInstance would cause us to lose the data from the fields only supported in stream workspace

[EspenAlbert]

Would this imply that we need to convert the streamWorkspace object to a streamInstance to call this?

Yes.

[... one day we might add features to stream workspace that we don't support for stream instance

This makes sense. Motivation for users to change.

Feel free to resolve

[EspenAlbert]

Great job! Thank you for addressing the comments 👏