feat: Support missing calls with multi-project the options

[JPeer264]

This adds more support for having multiple projects where the Rust API had already support. This only affects .newDeploy()

Closes #2902
Closes CLI-212

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 0060a64

[linear]

CLI-212 Align JS API between commands that accept multiple projects

[szokeasaurusrex]

@JPeer264, apologies I did not notice this earlier, but I just realized that the server actually completely ignores the projects supplied to the releases set-commits and releases finalize commands. Setting commits and finalizing releases seem to affect the release directly, and there is no way to scope such updates to a specific project. So, we should not add the ability to set projects for these to the JS API. I will modify the Rust code to ignore the --project for these commands — however, as the --project argument is a global flag, we will not fully remove the argument in the CLI side.

However, for deploys new, the server does respect the projects passed. If no projects are specified, we create the deploy for all projects on the release; otherwise, the deploy is only created for the specified projects.

[szokeasaurusrex]

Suggested change

	* The projects to deploy the release to. If not provided, the deployment will be created for the default project.
	* The projects to deploy the release to. If not provided, the deployment will be created for all projects associated with the release.

[szokeasaurusrex]

Also, does this change allow releases new to accept multiple projects?