Scaleapi

Bug Fixes
- Fixed platform "False 500 into 409" error on task creation
- When creating large volumes of tasks consecutively the platform can time out and return a `500` error even if a task was successfully created
- This triggers our retry logic which will then return a `409` Duplicate Resource error as the task being retried had already been created
- This specific series of events is now being handled gracefully

New Features
- Added method to set task metadata when specifying task id via `set_task_metadata`
- Added method to set metadata on Task object via `task.set_metadata`
- https://docs.scale.com/reference/set-metadata

Known Issues
- The platform can sometimes generate a false `500` error even when correctly creating a task. The Scale Python Client will retry when it receives a `500`, which can then lead to a `409` duplicate resource error. This behavior is most often seen when creating a high volume of tasks consecutively

New Features
- Added support for `clear_unique_id` parameter in `cancel_task` and `task.cancel()` methods
- https://github.com/scaleapi/scaleapi-python-client#cancel-task
- Scale API's two new endpoints to update and remove `unique_id` is implemented in SDK.
- `client.update_task_unique_id` and `task.update_unique_id`
- https://github.com/scaleapi/scaleapi-python-client#update-a-tasks-unique-id
- `client.clear_task_unique_id` and `task.clear_unique_id`
- https://github.com/scaleapi/scaleapi-python-client#clear-a-tasks-unique-id
- README updated with new examples for the changes above

Other Changes and Notes
- Delete type of API requests are now also getting retried

New Features
- Support for `studio` project creation

New Features
- Support `ReviewStatus.Pending` ready to review in the customer dashboard

Bug Fixes
- Remove empty payloads from GET requests to avoid erroring out upon contact with an AWS WAF