feat(stage): add support for starter workspaces

[nunogoncalves03]

We have recently updated the Stage Management API to add support for starter workspaces. Following this change, we would like to update the SingleStoreDB Python SDK to also accommodate starter workspaces in stage resources.

This PR introduces a basic StarterWorkspace object and modifies the Fusion SQL stage syntax. As discussed in Kanit's proposal, the IN GROUP syntax has been simplified to just IN. For example, the previous command SHOW STAGE FILES IN GROUP '{{ wg_name }}' has been updated to SHOW STAGE FILES IN '{{ wg_name }}'.

cc: @ricardoasmarques @kanitsharma

[nunogoncalves03]

Should I create separate PRs for the Python SDK and Fusion SQL changes?

[kesmit13]

I guess I'm a little confused by the changes here. It appears as though you are making the commands only work for starter workspaces and not for traditional ones. I'm saying this because of the change from get_workspace_group to get_starter_workspace. Is that the intent, or is get_starter_workspace intended to return either a starter workspace or a traditional one? If it returns either one, it shouldn't be named get_starter_workspace and the return type needs to include both StarterWorkspace and WorkspaceGroup.

We also probably need to create two SQL commands: one that keeps GROUP in the command and another than has it removed because we have already released the command with GROUP in it. I don't think we can just make GROUP optional in a single command because of abmiguities that would be in parsing.

[nunogoncalves03]

My bad, the get_starter_workspace function should be renamed to get_deployment, as it returns either a WorkspaceGroup or a StarterWorkspace.

Regarding the removal of the GROUP syntax, I misunderstood your comment on Kanit's proposal. I thought we were going to eliminate it rather than ensure backwards compatibility. That makes sense, I'll fix this.

[kesmit13]

I think it's fine to have duplicate commands for now. In fact, you can take what you have now and just copy the whole command and add a GROUP in the syntax so it works like it used to, but still works with both types of deployments. At some point, we can remove the old one.

[kesmit13]

I noticed that the wrong string had been used in the Arguments sections of the commands for anything that has a multi-word name. The syntax in the Arguments and Remarks should use - rather than _. The - version is what shows up in the Fusion help system. I realize you were just using the form that was there before, but if you could change all of those in this PR, that would be great. After that, I think it's ready to go.