Fix quicksearch relevance to show exact matches first

[JasonWildMe]

Summary

• Fix quicksearch returning results in arbitrary order by adding boosted queries and sorting
• Exact ID matches now appear first, followed by prefix matches, then partial matches
• Addresses the issue where searching "CRC-6" would not show individual "CRC-6" in top results

Root Cause

The quicksearch used only wildcard queries which return constant scores (1.0), causing OpenSearch to return results in arbitrary order.

Changes

Query Type	Field	Boost	Purpose
wildcard (exact)	id	100	"CRC-6" matches "CRC-6" exactly
term	names	80	Exact name match
wildcard (prefix)	id	50	"CRC" matches "CRC-6", "CRC-123"
prefix	names	40	Name starts with search term
wildcard (x)	id	10	Partial ID match
wildcard (x)	names	5	Partial name match
wildcard (x)	encounterIds	1	Encounter ID contains term

Additional changes:

• Added sort=id&sortOrder=asc for deterministic ordering
• Added minimum_should_match: 1 for explicit query behavior
• Used case_insensitive: true for ID field (no normalizer in mapping)

Test plan

• Existing unit tests pass
• Search "CRC-6" in Flukebook quicksearch - should show "CRC-6" as top result
• Search partial terms - should still return relevant matches
• Verify case-insensitive search works (e.g., "crc-6" finds "CRC-6")

Fixes #1541