Refactor Dataset create_data_rows_sync to use upsert

[vbrodsky]

Description

This PR introduces improvements to the data row creation process within the SDK. This PR refactors the following two data row creation methods:

• Dataset.create_data_row
• Dataset.create_data_row_sync

Both methods now leverage the upsert mutation for data row creation.

Since the upsert mutation is asynchronous, a task waiting mechanism has been implemented within these methods to ensure synchronous data row creation behavior.

A new ResourceCreationError exception has been introduced. This exception provides informative error messages in case of data creation failures, replacing the previous approach of returning None.

Stories: https://labelbox.atlassian.net/browse/PLT-1066 https://labelbox.atlassian.net/browse/PLT-1067

On test failures:

• User group creation tests fail, this PR should fix it
• A couple of tests failed due to data row creation task not completing. I have verified these tests pass when run on my laptop against stage

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Document change (fix typo or modifying any markdown files, code comments or anything in the examples folder only)

All Submissions

• [ ] Have you followed the guidelines in our Contributing document?
• [ ] Have you provided a description?
• [ ] Are your changes properly formatted?

New Feature Submissions

• [ ] Does your submission pass tests?
• [ ] Have you added thorough tests for your new feature?
• [ ] Have you commented your code, particularly in hard-to-understand areas?
• [ ] Have you added a Docstring?

Changes to Core Features

• [ ] Have you written new tests for your core changes, as applicable?
• [ ] Have you successfully run tests with your changes locally?
• [ ] Have you updated any code comments, as applicable?