[Bug]: Implement Debounced Search in Glossary

[suman20041]

Bug Description

The glossary search triggers on every keystroke, causing performance issues and unnecessary filtering operations that can slow down the user experience.

Steps to Reproduce

1. Navigate to the Glossary page
2. Start typing in the search input field
3. Observe that filtering triggers on every single character typed
4. Type rapidly and notice multiple filter operations executing in quick succession

Expected Behavior

• Search should only trigger after the user has stopped typing
• Should implement debouncing (currently 150ms but could be optimized)
• Should cache recent search results for better performance
• Should have minimum character requirement before searching

Actual Behavior

• Search fires on every keystroke without waiting
• Multiple unnecessary filter operations run in sequence
• No caching mechanism for repeated searches
• Searches even for single characters

Browser

Chrome

Operating System

No response

Logs / Screenshots

No response

[github-actions]

Thanks @suman20041! 👋
Your issue is important — maintainers will take a look soon.

Before contributing, please note:
🔹 Make sure you check #23 – Important Contributing Guidelines for OpenSource Compass
🔹 PRs should be raised only after the issue is assigned

[suman20041]

@sayeeg-11 Can you please assign this issue to me ??