feat: add support for custom field names in RQL struct tags

[whoAbhishekSah]

Description

This PR enhances the field lookup functionality in the RQL parser to support custom field names via struct tags. Previously, the parser only matched against struct field names. With this change, users can now define custom field names using the name parameter in RQL struct tags, enabling more flexible API schemas.

Changes

• Modified searchKeyInsideStruct function to check both struct field names and custom names defined in RQL tags
• Added support for name= parameter in RQL struct tags
• Maintained case-insensitive matching for both field names and custom names
• Preserved backward compatibility with existing struct definitions

Example Usage

// Before
type Organization struct {
    BillingPlanName string    `rql:"type=string"`
}
// Could only be queried using "BillingPlanName"

// After
type Organization struct {
    BillingPlanName string    `rql:"name=plan_name,type=string"`
}
// Can be queried using both "BillingPlanName" and "plan_name"

Benefits

• Allows for more intuitive API field names without changing struct field names
• Enables better separation between internal struct representation and external API schema
• Maintains backward compatibility with existing implementations
• Simplifies API versioning and field renaming

Testing

• Added unit tests for custom field name lookups
• Verified backward compatibility with existing struct definitions
• Tested case sensitivity handling