…o feat/support-for-update-records-from-SDK

Also, this class defines an generic type `R` for records.

The implementation will show a warning with an explicit message

Also, the question (id -> name) and question (name -> id) maps are computed from the original dataset

Records can be updated by assigning content and then call the `record.update` method.

Suggestions are still supported, so users can update a record by passing the suggestions. But a more general way should be:

```python
record.metadata.update({"new": "metadata"})
record.suggestions = (Suggestion....)

record.update()
```

…` workflow

Record suggestions can be modified locally to prepare changes and then call the `ds.updated_records` with modified suggestions. The `record.update` still support suggestions

```python
records = ds.records[:10]

for record in records:
   record.suggestions = [SuggestionSchema(...)]
   record.metadata.update({"new": "metadata"})

# Apply all local changes to remote records
ds.update_records(records)

```

…test dataset class

…=...) and `record.update()`

The suggestions will be filtered before update them if suggestions where provided in the `record.update` method. Otherwise, the record suggestions will be sent as new suggestions

…etter integration with unit tests

(A code review must be taken in order to not modify a class because the tests)

for more information, see https://pre-commit.ci

…:argilla-io/argilla into feat/support-for-update-records-from-SDK

…o feat/support-for-update-records-from-SDK

…o feat/support-for-update-records-from-SDK

Co-authored-by: Alvaro Bartolome <[email protected]>