add 'comment' field to collection apis (#3957)

[abhishek818]

helps in providing table metadata

fixes: #3957
/claim #3957

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?

New Feature Submissions:

1. Does your submission pass tests?
2. Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
3. Have you checked your code using cargo clippy --all --all-features command?

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?

[generall]

I would prefer to have a single optional string called comment

[abhishek818]

resolved.

[generall]

Hey @abhishek818, I believe the last step would be to trigger API schema gen https://github.com/qdrant/qdrant/blob/master/docs/DEVELOPMENT.md#rest

[timvisee]

@generall Do you think a comment field would be sufficient? I'd expect an interface that is a bit more fully-fledged; something like the payload API but on collection level.

[generall]

I'd expect an interface that is a bit more fully-fledged; something like the payload API but on collection level.

I would prefer to not over-complicate this. As I understood - the main use-case is o give more information about the collection than it would normally fit into the name.

If we would need payload-like data in the collection, we can make another change

[generall]

This PR requires ability to update the comment. And it doesn't look the comment even persisted