Remove deprecated PointsUpdateOperation variants

[coszio]

In Qdrant 1.7, we deprecated these fields. For 1.8, we can safely remove them. Edit: We will remove these eventually

Related PR: qdrant/qdrant-client#502

All Submissions:

• Contributions should target the dev branch. Did you create your branch from dev?
• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

[timvisee]

I'm unsure what effect removing these fields might have on our generated clients.

Tagging @generall for this opinion.

[agourlay]

@coszio have you tried generating the clients with this PR?
I'd say Python Rust & Go.

I assume that this will break clients using the deprecated types at least.

[coszio]

Python client was already using both fields (new and deprecated) at once, so removing one won't hurt as long as users weren't using the gRPC types directly.

For other clients like the Rust one which are dependent of only gRPC, this will be breaking, yes.

[coszio]

@generall do we want this change here, or only in client side?

[generall]

Only on client side for now

[coszio]

Drafting then