Fix/update collection dto partial

[AnneGerlach]

What this PR does / why we need it:

• This PR relaxes the typing of the UpdateCollection use case to allow partial collection updates.

• Native Dataverse collection updates do not require a fully populated object, only the fields to be changed need to be provided.

• This change aligns the client typing with that behavior and avoids unnecessary TypeScript warnings in downstream usage.

• This is a typing-only change with no runtime impact.

Which issue(s) this PR closes:

• Closes -

Related Dataverse PRs:

• Depends on -

Special notes for your reviewer:

• TypeScript typing change only (Partial)

• No API or runtime behavior changes

Suggestions on how to test this:

Is there a release notes or changelog update needed for this change?:

• Yes, small changelog entry

Additional documentation:

[ChengShi-1]

Thank you for the change and your contribution. This is a good point. I tested the native api, and it does support partial updates.

However, I think we may need to do more tweaks, if we want to change it to "partial". createCreateOrUpdateRequestBody() is currently written for create/full-update semantics. Also, the current frontend code and tests also rely on full-update semantics. If we want to support partial updates, we will likely need broader changes across the DTOs, request-building logic, and tests, since the current design is aligned around full replacement.

[ekraffmiller]

Thanks for the PR, it would be a good addition to allow this, since it is allowed on the API.
I agree with @ChengShi-1, the current implementation of createCreateOrUpdateRequestBody() needs to change, to allow for partially populated DTO. Also, a test to show that it update is successful with a partially populated DTO. With those changes, I think it could be merged.