User story: As an engineer/product manager, I want to add product area to an experiment so that I and other stakeholders can review how many experiments there are in our domain

Problem:
Experiments are currently difficult to group or analyse by product domain (e.g. Search, PDP, Checkout). As a result, programme reporting lacks clarity on where experimentation effort is concentrated, which areas are under‑ or over‑represented, and how different product areas are performing over time. This limits the ability to assess experimentation coverage, prioritisation, and strategic alignment.

Solution:
Add a Product Area field to experiments, using a controlled list of agreed domains. This enables consistent tagging of tests to the relevant product area, allowing experiments to be grouped, compared, and analysed meaningfully across the programme without relying on naming conventions or manual interpretation.