[Bug]: The value of consistency_level returned by describe collection is a number rather than a corresponding semantic term, which is not user-friendly.

[zhuwenxing]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

'consistency_level': 0

{'collection_name': 'client_geometry_3yiyc8Bb', 'auto_id': False, 'num_shards': 1, 'description': 'test geometry collection', 'fields': [{'field_id': 100, 'name': 'id', 'description': '', 'type': <DataType.INT64: 5>, 'params': {}, 'is_primary': True}, {'field_id': 101, 'name': 'vector', 'description': '', 'type': <DataType.FLOAT_VECTOR: 101>, 'params': {'dim': 128}}, {'field_id': 102, 'name': 'geo', 'description': '', 'type': <DataType.GEOMETRY: 24>, 'params': {}}], 'functions': [], 'aliases': [], 'collection_id': 460756692454159104, 'consistency_level': 0, 'properties': {}, 'num_partitions': 1, 'enable_dynamic_field': False, 'created_timestamp': 460829215984713733, 'update_timestamp': 460829215984713733}

Expected Behavior

No response

Steps/Code To Reproduce behavior

Environment details

- Hardware/Softward conditions (OS, CPU, GPU, Memory):
- Method of installation (Docker, or from source):
- Milvus version (v0.3.1, or v0.4.0):
- Milvus configuration (Settings you made in `server_config.yaml`):

Anything else?

pymilvus version: 2.5.16rc3