Metrics, data collection, feature enablement/ experiments have components that nest under Internals.  From that perspective the component is in a predictable/ consistent location and seems well parented.  

What's the rationale for wanting to migrate it to Blink, which describes properties/ features of the renderer?

Agreed that origin trials is about feature experiments, and includes data collection. Conceptually this is similar to field trials (and led to how we came up with the naming). A few key differences:
- Origin trials are about experimenting with web platform features (not browser features)
- Origin trials are intentionally visible to web developers. Web developers must explicitly opt-in to the experiments, and we collect their feedback.

In other words, origin trials are all about experimentation on the web platform. Origin trials are not internal to Chromium. In general, I think Blink is more that just properties or features of the renderer. As others have said "Blink is Chromium project's implementation of the Web Platform".

Ping. Could I get an update on this request?

Internals isn't specific to Chromium, it just means the internal modules/ services that service the overall project (e.g. Skia, media, etc... are directly relevant to the Web Platform).

For the sake of consistency, let's keep this in Internals and keep Blink>* about the features on the web platform (i.e. like other components I don't want to see duplicate trees emerge under functional categorizations).