Fix Case Sensitivity Inconsistency in API Key References

[Salman-Ahamed]

🎯 What’s this PR about?

Resolved the case sensitivity inconsistency between Vault page and Builder components when handling API key references. Previously, Builder treated key references as case-sensitive while Vault allowed case variations, causing failed key lookups and confusing error messages when users referenced keys with different casing (e.g., 'Hello' vs 'hello').

###✅ Changes Included

• Updated key name comparison logic to be case-insensitive by converting both key names and vault entry names to lowercase
• Fixed key lookup failures for case mismatches between Vault and Builder
• Eliminated false'missing key' notifications when keys exist with different casing
• Prevented uniqueness errors when attempting to create keys that already exist with different case

---

📎 Related ClickUp Ticket

ClickUp: https://app.clickup.com/t/86euj8yx9

---

💻 Demo (optional)

---

✅ Checklist

• Self-reviewed the code
• Linked the correct ClickUp ticket
• Tested locally (MANDATORY)
• Marked as Draft if not ready for review

[Salman-Ahamed]

reviewed