Add `exact_match` option to schema's field parameters

Description:

Currently, the only way to achieve exact string matching in Typesense is by adding characters to symbols_to_index. However, this approach applies to all fields in the collection, which may not always be desirable.

Steps to Reproduce:

1. Set a field of type string[] in your schema, such as sizes.
2. Insert documents with values like ["11.5", "12", "4.5"] for the sizes field.
3. Try filtering using the sizes field with the value 45.

Expected Behavior:

The filter should return documents that exactly match the value 45. No documents containing 4.5 should be included in the results.

Actual Behavior:

The filter returns documents that include 4.5, despite not being an exact match to 45.

Proposed Solution:

Introduce an exact_match parameter to field definitions within the schema. When set to true, this parameter should enforce exact matching for the field during filtering operations.

Metadata:

• Typesense Version: v27.0
• OS: Cloud

Start by reproducing the string[] sizes case described in the issue, then trace schema field definitions into the filtering operations that handle field parameters. Done means an exact_match option can be enabled for an individual field and filtering for 45 excludes values such as 4.5 without changing other fields.