SM-417: Add project create, update, and delete commands

[coltonhurst]

Type of change

- [ ] Bug fix
- [x] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

Adds the ability to create, update, and delete projects via the Bitwarden SDK.

This was originally under the SM-417 internal ticket, but is now more specifically represented by the child SM-783 internal ticket.

Code changes

• client.rs: Add the project create, update, and delete commands for matching in the run function
• client_projects.rs: Add the create, update, and delete functions
• projects.rs: Add the implementations for the create_project, update_project, and delete_project project commands
• command.rs: Add the project create, update, and delete commands to the ProjectsCommand enum
• projects_request.rs: Add the ProjectCreateRequest, ProjectPutRequest, and the ProjectsDeleteRequest structs that are the request models
• projects_response.rs: Add the ProjectsDeleteResponse and ProjectDeleteResponse structs that are the response models

All other schema update file changes were generated by npm run schemas.

Before you submit

• Please add unit tests where it makes sense to do so (encouraged but not required)

[dani-garcia]

Looks like a great start, thanks @coltonhurst!

A small thing missing, we have to add the new create, update, delete commands to the big command struct here:

sdk/crates/bitwarden/src/sdk/request/command.rs

Lines 120 to 127 in 9e2e04c

	pub enum ProjectsCommand {
	/// > Requires Authentication
	/// > Requires using an Access Token for login or calling Sync at least once
	/// Retrieve a project by the provided identifier
	///
	/// Returns: [ProjectResponse](crate::sdk::response::projects_response::ProjectResponse)
	///
	Get(ProjectGetRequest),

And then use it here:

sdk/crates/bitwarden-json/src/client.rs

Line 57 in 9e2e04c

Command::Projects(cmd) => match cmd {

That way the new commands can be used both directly with the rust crate but also from the JSON wrapper and all the language bindings.

[Hinton]

Two minor comments, looks good otherwise!

[Hinton]

Should this be called updateRequest? Put feels like an implementation detail.

[coltonhurst]

This was to follow the convention in secrets_request.rs which uses SecretPutRequest. We definitely can refactor out Put in multiple locations and use Update though. This could be done in a different ticket, this one, or we take a different approach?

[coltonhurst]

Discussed this, we will address this in a separate PR

[Hinton]

Isn't enc already defined above? I think we can reuse it.

[coltonhurst]

Hmm, any recommendations on a better way to do this? By removing it we break one of the borrowing rules. With it removed we have the following error, the compiler delineates the following:

• immutable borrow on line 35/36
• mutable borrow on line 46
• immutable borrow on line 54

cannot borrow *client as mutable because it is also borrowed as immutable

[coltonhurst]

Discussed with @dani-garcia, addressing this in this PR: #70

[Hinton]

Same

[coltonhurst]

Same as here

[coltonhurst]

Update here