[CDX-255] Expose features object in request models

[TarekAlQaddy]

• Add features to Search and Browse response models
• Add tests
• features & feature_variants that are inside the request object of the response can be accessed as the request object is a generic Map<String, Object>
  • Ex: Map<String, Object> features = (Map<String, Object>) response.getRequest().get("features");
System.out.println(features.get("personalization"));

[Copilot]

Pull Request Overview

This PR adds support for exposing features and feature variants from search and browse API responses by adding new model classes and updating response models.

• Added new Feature and Variant model classes to represent feature data
• Updated SearchResponseInner and BrowseResponseInner to include features list
• Added comprehensive test coverage for the new features functionality

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
Feature.java	New model class representing a feature with display name, feature name, enabled status, and variant
Variant.java	New model class representing a feature variant with name and display name
SearchResponseInner.java	Added features field and getter/setter methods
BrowseResponseInner.java	Added features field and getter/setter methods
SearchResponseTest.java	Added test case to verify features parsing in search responses
BrowseResponseTest.java	Added test case to verify features parsing in browse responses

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Mudaafi]

LGTM, I checked the schemas in the autocomplete repo and they match the structure we have here.

[Mudaafi]

Can we also test the case where variant is null? Something like ****

Suggested change

	assertEquals(
	"browse result feature variant [display name] exists",
	response.getResponse().getFeatures().get(0).getVariant().getDisplayName(),
	"Default weights");
	assertEquals(
	"browse result feature variant [name] exists",
	response.getResponse().getFeatures().get(0).getVariant().getName(),
	"default_rules");
	}
	assertEquals(
	"browse result feature variant [display name] exists",
	response.getResponse().getFeatures().get(0).getVariant().getDisplayName(),
	"Default weights");
	assertEquals(
	"browse result feature variant [name] exists",
	response.getResponse().getFeatures().get(0).getVariant().getName(),
	"default_rules");
	assertEquals(
	"browse result feature variant returns null if empty",
	response.getResponse().getFeatures().get(1).getVariant(),
	null);
	}

[Mudaafi]

Same as above for Browse Tests

[Mudaafi]

Tests are failing due to an unrelated API updates. I've created a story internally to fix.